Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7f7b64e3e3886d9a6107cdc492f771e94fc4338818ef2bc9ac0898789e3702a

Tx prefix hash: e7fdd5a8e51baef0ffd23049b95f739a14fad9045015e61e28b3d88a21288edf
Tx public key: 754e5cbae0b8ed2bb3a696606cda40191a9aa75ae180dbd1badfc3a43cf2b25e
Timestamp: 1763619871 Timestamp [UCT]: 2025-11-20 06:24:31 Age [y:d:h:m:s]: 00:033:02:03:26
Block: 1416056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23693 RingCT/type: yes/0
Extra: 01754e5cbae0b8ed2bb3a696606cda40191a9aa75ae180dbd1badfc3a43cf2b25e02110000000934af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94bdfbc7703947f9e328926965e232fb4d14adf9cf516e19a8379f9e27e6f60e 0.600000000000 1904575 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": 1416066, "vin": [ { "gen": { "height": 1416056 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94bdfbc7703947f9e328926965e232fb4d14adf9cf516e19a8379f9e27e6f60e" } } ], "extra": [ 1, 117, 78, 92, 186, 224, 184, 237, 43, 179, 166, 150, 96, 108, 218, 64, 25, 26, 154, 167, 90, 225, 128, 219, 209, 186, 223, 195, 164, 60, 242, 178, 94, 2, 17, 0, 0, 0, 9, 52, 175, 49, 204, 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