Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 072e097a64bbba21634592a9d5e8c92be28a7c3f9c989e3747cd2f7fc4e4e188

Tx prefix hash: 8517fda8f62ca43f46701582ef2bd40bd22bfd11ab4ed95a3f8091eb57f0ba7c
Tx public key: 3f6d578562f60fd75e0588c3373a3bf61ceff0a8b3469333b7145617e53c96c4
Timestamp: 1729682793 Timestamp [UCT]: 2024-10-23 11:26:33 Age [y:d:h:m:s]: 00:141:16:43:40
Block: 1137801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101072 RingCT/type: yes/0
Extra: 013f6d578562f60fd75e0588c3373a3bf61ceff0a8b3469333b7145617e53c96c402110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 384296bcb11357cf63ded3d3bf81717f7ebd0953e6dc160c8ab7063fff985af9 0.600000000000 1621362 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": 1137811, "vin": [ { "gen": { "height": 1137801 } } ], "vout": [ { "amount": 600000000, "target": { "key": "384296bcb11357cf63ded3d3bf81717f7ebd0953e6dc160c8ab7063fff985af9" } } ], "extra": [ 1, 63, 109, 87, 133, 98, 246, 15, 215, 94, 5, 136, 195, 55, 58, 59, 246, 28, 239, 240, 168, 179, 70, 147, 51, 183, 20, 86, 23, 229, 60, 150, 196, 2, 17, 0, 0, 0, 10, 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