Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00de02547172673d13028124e267252052fa850ea8dd2f2df5b248417a23415a

Tx prefix hash: dc10fe6260cd1ff319567b54b7c2f1f5bd4f81a9b3dac80a814cb9bac2c3e81f
Tx public key: 7801872c6bcc613d4df957e8690b0f011560de5cb496c474de63a557df1a5736
Timestamp: 1737707949 Timestamp [UCT]: 2025-01-24 08:39:09 Age [y:d:h:m:s]: 00:049:16:09:09
Block: 1204165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35324 RingCT/type: yes/0
Extra: 017801872c6bcc613d4df957e8690b0f011560de5cb496c474de63a557df1a5736021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36b341926d8f7a59d3a9f83324c4f0d17b8de80c8c75bcd04b89f0bd99138106 0.600000000000 1690848 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": 1204175, "vin": [ { "gen": { "height": 1204165 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36b341926d8f7a59d3a9f83324c4f0d17b8de80c8c75bcd04b89f0bd99138106" } } ], "extra": [ 1, 120, 1, 135, 44, 107, 204, 97, 61, 77, 249, 87, 232, 105, 11, 15, 1, 21, 96, 222, 92, 180, 150, 196, 116, 222, 99, 165, 87, 223, 26, 87, 54, 2, 17, 0, 0, 0, 9, 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