Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cec0af94c04e0bfc3381703ac1d6e95fe0421ec992ab83d09891032a69713f4c

Tx prefix hash: 46209e8b18a2fe38f7affef44977fd9e88e0cd2c632f098d7c143fd585cd6ac7
Tx public key: a36113cf3c5c3e9d38f9157ea05d5566976ad000b1f78fbfc7fda1796bddfd15
Timestamp: 1706596362 Timestamp [UCT]: 2024-01-30 06:32:42 Age [y:d:h:m:s]: 01:137:15:16:04
Block: 946406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359400 RingCT/type: yes/0
Extra: 01a36113cf3c5c3e9d38f9157ea05d5566976ad000b1f78fbfc7fda1796bddfd150211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8cc0b07b075801ed9bec9fed2b3b6acf74a9a89eec00871302aab99e43c3684a 0.600000000000 1404738 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": 946416, "vin": [ { "gen": { "height": 946406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8cc0b07b075801ed9bec9fed2b3b6acf74a9a89eec00871302aab99e43c3684a" } } ], "extra": [ 1, 163, 97, 19, 207, 60, 92, 62, 157, 56, 249, 21, 126, 160, 93, 85, 102, 151, 106, 208, 0, 177, 247, 143, 191, 199, 253, 161, 121, 107, 221, 253, 21, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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