Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ecf1a5a9a24376b09e06bca4b9bc10ae8cf1c28c5763e7251b9ed869d613a69

Tx prefix hash: 8d4b738c3858ab6b4b0ae5448f43133844176e5848698ca96710d6d85be414b9
Tx public key: bc1e1f8d030b06884c5220b2a1969a1124c51b2b63f109a040553292c164c688
Timestamp: 1710689065 Timestamp [UCT]: 2024-03-17 15:24:25 Age [y:d:h:m:s]: 01:018:02:32:04
Block: 980381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273904 RingCT/type: yes/0
Extra: 01bc1e1f8d030b06884c5220b2a1969a1124c51b2b63f109a040553292c164c68802110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c600a9839c873a82423cd443b9b0eddb6eac3d25feb5e933324b490c49a030d7 0.600000000000 1440446 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": 980391, "vin": [ { "gen": { "height": 980381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c600a9839c873a82423cd443b9b0eddb6eac3d25feb5e933324b490c49a030d7" } } ], "extra": [ 1, 188, 30, 31, 141, 3, 11, 6, 136, 76, 82, 32, 178, 161, 150, 154, 17, 36, 197, 27, 43, 99, 241, 9, 160, 64, 85, 50, 146, 193, 100, 198, 136, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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