Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67a477e0e084c918d89b7e3a748d506d5d67c1b7a0bbfd75ad743bb9a0be84d5

Tx prefix hash: 68a5ac7ba3d3f85654b440f1a0281da6b15497ebc7323909ae6c2880bd9574ee
Tx public key: aeef5e9d052a3cbb2a8acb00bfdbe824c7bd03e4a997adc0b5edf7d548c38443
Timestamp: 1735104718 Timestamp [UCT]: 2024-12-25 05:31:58 Age [y:d:h:m:s]: 00:093:16:45:27
Block: 1182664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66743 RingCT/type: yes/0
Extra: 01aeef5e9d052a3cbb2a8acb00bfdbe824c7bd03e4a997adc0b5edf7d548c384430211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d0d1a53af5430552626a3720c2983cdad5c9882f2241e42ff33da85f0df1beb 0.600000000000 1669099 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": 1182674, "vin": [ { "gen": { "height": 1182664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d0d1a53af5430552626a3720c2983cdad5c9882f2241e42ff33da85f0df1beb" } } ], "extra": [ 1, 174, 239, 94, 157, 5, 42, 60, 187, 42, 138, 203, 0, 191, 219, 232, 36, 199, 189, 3, 228, 169, 151, 173, 192, 181, 237, 247, 213, 72, 195, 132, 67, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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