Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 064a8a4023bbabc135b0c42e9dadb33e5f370f79ef12f59e1ce2388cf0d0bf33

Tx prefix hash: d22faaf07b94dbe1873a9dd033577da2b6b61f51546556d2683e1c7207b6b154
Tx public key: be5a0088a202a7a6acfbae831c129b772f5e70b982e6bf8743f3c83176885e8b
Timestamp: 1717499440 Timestamp [UCT]: 2024-06-04 11:10:40 Age [y:d:h:m:s]: 00:141:00:05:45
Block: 1036834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100966 RingCT/type: yes/0
Extra: 01be5a0088a202a7a6acfbae831c129b772f5e70b982e6bf8743f3c83176885e8b0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ebd8e6ccc387e82c9634846cf6fd501ad54c4472a2c32e34a08bacb0629657e6 0.600000000000 1505363 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": 1036844, "vin": [ { "gen": { "height": 1036834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ebd8e6ccc387e82c9634846cf6fd501ad54c4472a2c32e34a08bacb0629657e6" } } ], "extra": [ 1, 190, 90, 0, 136, 162, 2, 167, 166, 172, 251, 174, 131, 28, 18, 155, 119, 47, 94, 112, 185, 130, 230, 191, 135, 67, 243, 200, 49, 118, 136, 94, 139, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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