Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73a12f215a44f752a8e5eac471ae4d4583e62dc10b3c2a080414eb00e34489eb

Tx prefix hash: cc788c801ad286c0fc4791255eb45950e0aa36c9e0495ca60fa845ca79d8a06e
Tx public key: a20bce1ff657e1cff687ee942b3c28be701f70f95d78bc5a9cff977541a814fc
Timestamp: 1734803199 Timestamp [UCT]: 2024-12-21 17:46:39 Age [y:d:h:m:s]: 00:101:12:17:33
Block: 1180190 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72301 RingCT/type: yes/0
Extra: 01a20bce1ff657e1cff687ee942b3c28be701f70f95d78bc5a9cff977541a814fc021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3aac2d63c6d65cf62a44e81995a3eb2c6622c7bb29ff605510cd48af2acc81e 0.600000000000 1666597 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": 1180200, "vin": [ { "gen": { "height": 1180190 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3aac2d63c6d65cf62a44e81995a3eb2c6622c7bb29ff605510cd48af2acc81e" } } ], "extra": [ 1, 162, 11, 206, 31, 246, 87, 225, 207, 246, 135, 238, 148, 43, 60, 40, 190, 112, 31, 112, 249, 93, 120, 188, 90, 156, 255, 151, 117, 65, 168, 20, 252, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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