Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82ee91e8b26c3cd02938f2eec083a3dba21ebc4a9ac383010ddd11e956a3a23c

Tx prefix hash: 1f7fea311bd390d3efcb6773fb6eae722410460b71da2fe71e04c6cb1351685e
Tx public key: d537f4a4390b5d5a647125ab80c468463a94fb9c33e73bc63ec41078c1b5ad9d
Timestamp: 1723811223 Timestamp [UCT]: 2024-08-16 12:27:03 Age [y:d:h:m:s]: 00:251:23:53:59
Block: 1089152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179996 RingCT/type: yes/0
Extra: 01d537f4a4390b5d5a647125ab80c468463a94fb9c33e73bc63ec41078c1b5ad9d021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8f19af8391b3e17bccb80c2688f65796800687a59f5f515a2ff44f463594a66 0.600000000000 1563771 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": 1089162, "vin": [ { "gen": { "height": 1089152 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8f19af8391b3e17bccb80c2688f65796800687a59f5f515a2ff44f463594a66" } } ], "extra": [ 1, 213, 55, 244, 164, 57, 11, 93, 90, 100, 113, 37, 171, 128, 196, 104, 70, 58, 148, 251, 156, 51, 231, 59, 198, 62, 196, 16, 120, 193, 181, 173, 157, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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