Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 8c8084bd71c0c442e8851caf3e59dfd55ccf3a8f8d35257d2e61a52a511c6d71

Tx prefix hash: 764392cf8248bcba7c1fcbb3f28d0e2127f1a64641a3bea8cae9886f9bb5f71b
Tx public key: 2832588dd89a9b5e2c7835db1a59eb9ddd7286f41d3f39db929563875289e0bc
Timestamp: 1716033563 Timestamp [UCT]: 2024-05-18 11:59:23 Age [y:d:h:m:s]: 01:006:13:50:51
Block: 1024675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265625 RingCT/type: yes/0
Extra: 012832588dd89a9b5e2c7835db1a59eb9ddd7286f41d3f39db929563875289e0bc02110000001259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e214967b94b45f9cfc9a0e997ab27bd406fc4412461aaa1d1559c3ca29907804 0.600000000000 1490606 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1024685, "vin": [ { "gen": { "height": 1024675 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e214967b94b45f9cfc9a0e997ab27bd406fc4412461aaa1d1559c3ca29907804" } } ], "extra": [ 1, 40, 50, 88, 141, 216, 154, 155, 94, 44, 120, 53, 219, 26, 89, 235, 157, 221, 114, 134, 244, 29, 63, 57, 219, 146, 149, 99, 135, 82, 137, 224, 188, 2, 17, 0, 0, 0, 18, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8