Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aad213f72903a3af1aecc5bf3a5693e9badbff924a33a11f70024a123dc08fca

Tx prefix hash: 826e4ddc16859a8b78534bb4a9531a586ef61fb0e1f145314efc203fd7181d3f
Tx public key: 9518321baebd6b2e6224003b8b0501ea2f2bf36ce8008595f60818c99ca1a015
Timestamp: 1716735758 Timestamp [UCT]: 2024-05-26 15:02:38 Age [y:d:h:m:s]: 00:311:08:01:21
Block: 1030509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222492 RingCT/type: yes/0
Extra: 019518321baebd6b2e6224003b8b0501ea2f2bf36ce8008595f60818c99ca1a0150211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2144eb6f0f76f7d563edb912fc40724c717c4c62a568e0dfcfcd214e4ffa31a5 0.600000000000 1498764 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": 1030519, "vin": [ { "gen": { "height": 1030509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2144eb6f0f76f7d563edb912fc40724c717c4c62a568e0dfcfcd214e4ffa31a5" } } ], "extra": [ 1, 149, 24, 50, 27, 174, 189, 107, 46, 98, 36, 0, 59, 139, 5, 1, 234, 47, 43, 243, 108, 232, 0, 133, 149, 246, 8, 24, 201, 156, 161, 160, 21, 2, 17, 0, 0, 0, 1, 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