Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 721c7ad6340bf6238a499cff2f70e1fe96f6c4173af29e395ec54345e9aa0dfa

Tx prefix hash: 5629ca1d4776706c845b501511b87f098c7b17fc267c6067f0f4c362490a1a4f
Tx public key: 5651ae3a9e630656a82995e2c2881799fadc96d38585c463b773527f964f582b
Timestamp: 1729102316 Timestamp [UCT]: 2024-10-16 18:11:56 Age [y:d:h:m:s]: 00:210:12:02:17
Block: 1133011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150258 RingCT/type: yes/0
Extra: 015651ae3a9e630656a82995e2c2881799fadc96d38585c463b773527f964f582b021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8237dc356ec6478e090b1585e97118c4ecdcfc98769d7e337663388cfc5634df 0.600000000000 1616076 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": 1133021, "vin": [ { "gen": { "height": 1133011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8237dc356ec6478e090b1585e97118c4ecdcfc98769d7e337663388cfc5634df" } } ], "extra": [ 1, 86, 81, 174, 58, 158, 99, 6, 86, 168, 41, 149, 226, 194, 136, 23, 153, 250, 220, 150, 211, 133, 133, 196, 99, 183, 115, 82, 127, 150, 79, 88, 43, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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