Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f92e06ec24624fd098aacdc54f3964a9781c000b5311768e27d1d39fa1b4007

Tx prefix hash: 39db81ce2945766e60e6baf6fda8af8ca75243b85fe7b84c7888ef0bfec3ece7
Tx public key: 1e20ec5e6f9ee2a0dc91c2d47ab593faaed421ed1909fbd38801729a3dedef04
Timestamp: 1726012284 Timestamp [UCT]: 2024-09-10 23:51:24 Age [y:d:h:m:s]: 00:251:05:17:44
Block: 1107401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179411 RingCT/type: yes/0
Extra: 011e20ec5e6f9ee2a0dc91c2d47ab593faaed421ed1909fbd38801729a3dedef0402110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64c410a8d5f980be2108d766874c296edec42ab7dc60b9c3fc06f3a7856e1f90 0.600000000000 1585012 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": 1107411, "vin": [ { "gen": { "height": 1107401 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64c410a8d5f980be2108d766874c296edec42ab7dc60b9c3fc06f3a7856e1f90" } } ], "extra": [ 1, 30, 32, 236, 94, 111, 158, 226, 160, 220, 145, 194, 212, 122, 181, 147, 250, 174, 212, 33, 237, 25, 9, 251, 211, 136, 1, 114, 154, 61, 237, 239, 4, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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