Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15499ca0fc879071ba627dfaa56f4d79b24c3a95b98e7698dd2bfcc41fcab54b

Tx prefix hash: 125f0abdaaea20771aa17575f74fefe033d7ea313479154e94b78c1bee8b8078
Tx public key: 67424ae8ecc53f6a0d28d4b3f9b27f820ccd5c3d121a2d3db64a4485197de8b6
Timestamp: 1695578856 Timestamp [UCT]: 2023-09-24 18:07:36 Age [y:d:h:m:s]: 01:228:07:42:50
Block: 855289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 424269 RingCT/type: yes/0
Extra: 0167424ae8ecc53f6a0d28d4b3f9b27f820ccd5c3d121a2d3db64a4485197de8b6021100000001faf35c9c000000000000000000

1 output(s) for total of 0.899647846000 dcy

stealth address amount amount idx
00: bb2cf7a7f58364f6392ce0a288dcfe8bcc632af84a9dde75c52fe38ca79fc478 0.899647846000 1309305 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": 855299, "vin": [ { "gen": { "height": 855289 } } ], "vout": [ { "amount": 899647846, "target": { "key": "bb2cf7a7f58364f6392ce0a288dcfe8bcc632af84a9dde75c52fe38ca79fc478" } } ], "extra": [ 1, 103, 66, 74, 232, 236, 197, 63, 106, 13, 40, 212, 179, 249, 178, 127, 130, 12, 205, 92, 61, 18, 26, 45, 61, 182, 74, 68, 133, 25, 125, 232, 182, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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