Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e5ec90b0b9adb8d18b605fc3fbf6b300749d27db320687451900803c7958b6c

Tx prefix hash: 22740baa1d53116d0f09cd8412a0011ab5df5bea5d1c6a30bae123385c5f86f1
Tx public key: 6deced23838b3ceefd343dadbfeedc6a0a6222cbce2c4bb9226073a8e7593273
Timestamp: 1716997953 Timestamp [UCT]: 2024-05-29 15:52:33 Age [y:d:h:m:s]: 00:356:03:04:46
Block: 1032666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254563 RingCT/type: yes/0
Extra: 016deced23838b3ceefd343dadbfeedc6a0a6222cbce2c4bb9226073a8e75932730211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68a846d6d1e8d379b6d97adbbd6fbb26bb5b1e7c67a56d35ebdadc99b3d68420 0.600000000000 1501119 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": 1032676, "vin": [ { "gen": { "height": 1032666 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68a846d6d1e8d379b6d97adbbd6fbb26bb5b1e7c67a56d35ebdadc99b3d68420" } } ], "extra": [ 1, 109, 236, 237, 35, 131, 139, 60, 238, 253, 52, 61, 173, 191, 238, 220, 106, 10, 98, 34, 203, 206, 44, 75, 185, 34, 96, 115, 168, 231, 89, 50, 115, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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