Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77e42b5aa5c1e89a293bc659e6caa9f59e65a3c8c74a75b87d27a5cd0d1302d4

Tx prefix hash: 71997d3dc9bfb4fb609c588a273148217efbf4fb94aca92ed0287d2813a591d2
Tx public key: 629dc6a605a07b942e25fff45ebf53ee08880ef621296bc31fce74781a10bb14
Timestamp: 1736699851 Timestamp [UCT]: 2025-01-12 16:37:31 Age [y:d:h:m:s]: 00:091:09:08:39
Block: 1195863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65114 RingCT/type: yes/0
Extra: 01629dc6a605a07b942e25fff45ebf53ee08880ef621296bc31fce74781a10bb140211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13445ed0a2a2c2dc7e35c49e0c127e51cfc0523d2d50f206211f91752914ffc5 0.600000000000 1682456 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": 1195873, "vin": [ { "gen": { "height": 1195863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13445ed0a2a2c2dc7e35c49e0c127e51cfc0523d2d50f206211f91752914ffc5" } } ], "extra": [ 1, 98, 157, 198, 166, 5, 160, 123, 148, 46, 37, 255, 244, 94, 191, 83, 238, 8, 136, 14, 246, 33, 41, 107, 195, 31, 206, 116, 120, 26, 16, 187, 20, 2, 17, 0, 0, 0, 1, 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