Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ae422587fa010e450511a143997fa67b63553e46f37efff06aa4894c29d5813

Tx prefix hash: 3fa557039c621b24bd3396bc38f1dc029f5a1711369e24a81a975ccb1c470b6f
Tx public key: 314d5e2cff9b0a9b8d33d23aacbe6db7ac2ffe7affbc12bef35be2579b44aeb5
Timestamp: 1745595802 Timestamp [UCT]: 2025-04-25 15:43:22 Age [y:d:h:m:s]: 00:208:10:07:51
Block: 1269246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146679 RingCT/type: yes/0
Extra: 01314d5e2cff9b0a9b8d33d23aacbe6db7ac2ffe7affbc12bef35be2579b44aeb50211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eed7405455803d328a9a59bdee10b71c91e2a7a047986e4cdcb38afd3d47af7a 0.600000000000 1756481 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": 1269256, "vin": [ { "gen": { "height": 1269246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eed7405455803d328a9a59bdee10b71c91e2a7a047986e4cdcb38afd3d47af7a" } } ], "extra": [ 1, 49, 77, 94, 44, 255, 155, 10, 155, 141, 51, 210, 58, 172, 190, 109, 183, 172, 47, 254, 122, 255, 188, 18, 190, 243, 91, 226, 87, 155, 68, 174, 181, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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