Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29cee84e923d59ae5fbf999328b3f1bd7fd0a20dce6a62c30e6c2cfccf1372fb

Tx prefix hash: 526eca700a80a05cf6f4cf3d84211154c1ab172209b7932b9bdfb76fd61cb344
Tx public key: 58ef0ba4d2d596074c05019850e5fcde08fb590cce8f9fa0c6f30768432bfcbf
Timestamp: 1701913281 Timestamp [UCT]: 2023-12-07 01:41:21 Age [y:d:h:m:s]: 02:024:15:32:29
Block: 907604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 537414 RingCT/type: yes/0
Extra: 0158ef0ba4d2d596074c05019850e5fcde08fb590cce8f9fa0c6f30768432bfcbf021100000005faf35c9c000000000000000000

1 output(s) for total of 0.603574879000 dcy

stealth address amount amount idx
00: 019fa4df9bc99befcbe4e65f8c1e4a0048cb860f1aaea838b9c0b8525941e815 0.603574879000 1364597 of 0

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": 907614, "vin": [ { "gen": { "height": 907604 } } ], "vout": [ { "amount": 603574879, "target": { "key": "019fa4df9bc99befcbe4e65f8c1e4a0048cb860f1aaea838b9c0b8525941e815" } } ], "extra": [ 1, 88, 239, 11, 164, 210, 213, 150, 7, 76, 5, 1, 152, 80, 229, 252, 222, 8, 251, 89, 12, 206, 143, 159, 160, 198, 243, 7, 104, 67, 43, 252, 191, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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