Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e3a03d410d3bf81d03c5e89fb0ad16716dcd090d325d67e981732e1d3d556bc

Tx prefix hash: 253a75c01852147fc910120425bd3c1b546eafc877656da3be6b8db2c7d9e10c
Tx public key: 99976cdec0b95cbc0aa37e019b31f4dce7babc70132a8195dbf64a61bb81a298
Timestamp: 1696697557 Timestamp [UCT]: 2023-10-07 16:52:37 Age [y:d:h:m:s]: 01:184:19:01:55
Block: 864565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393123 RingCT/type: yes/0
Extra: 0199976cdec0b95cbc0aa37e019b31f4dce7babc70132a8195dbf64a61bb81a29802110000000275e3f0e9000000000000000000

1 output(s) for total of 0.838179997000 dcy

stealth address amount amount idx
00: e28f2202b764c53ff64cca9740e0179ff5f1165efe66fb0b6c77150841573a5a 0.838179997000 1319085 of 0

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": 864575, "vin": [ { "gen": { "height": 864565 } } ], "vout": [ { "amount": 838179997, "target": { "key": "e28f2202b764c53ff64cca9740e0179ff5f1165efe66fb0b6c77150841573a5a" } } ], "extra": [ 1, 153, 151, 108, 222, 192, 185, 92, 188, 10, 163, 126, 1, 155, 49, 244, 220, 231, 186, 188, 112, 19, 42, 129, 149, 219, 246, 74, 97, 187, 129, 162, 152, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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