Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ec964637f2bd2b61a3525b7417e124845021f51ea85c7fa23e48f200da66546

Tx prefix hash: 693df7a0cfdd584a479a94b75740b47e98e0fc9745d969d421f5bdb9cce7e0c3
Tx public key: 954d2d0d4555140c22a9244269fdac7ff3ae02fe110a00d1cd4ad552fbc73ec0
Timestamp: 1636655896 Timestamp [UCT]: 2021-11-11 18:38:16 Age [y:d:h:m:s]: 03:167:10:24:03
Block: 372278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 898076 RingCT/type: yes/0
Extra: 01954d2d0d4555140c22a9244269fdac7ff3ae02fe110a00d1cd4ad552fbc73ec002110000000ff79c6ccf000000000000000000

1 output(s) for total of 35.850993337000 dcy

stealth address amount amount idx
00: c95e58b6bae669166a5ed9c57f95cbf85cd854e50dd409047cb83b9d3d8bf1d0 35.850993337000 754160 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": 372288, "vin": [ { "gen": { "height": 372278 } } ], "vout": [ { "amount": 35850993337, "target": { "key": "c95e58b6bae669166a5ed9c57f95cbf85cd854e50dd409047cb83b9d3d8bf1d0" } } ], "extra": [ 1, 149, 77, 45, 13, 69, 85, 20, 12, 34, 169, 36, 66, 105, 253, 172, 127, 243, 174, 2, 254, 17, 10, 0, 209, 205, 74, 213, 82, 251, 199, 62, 192, 2, 17, 0, 0, 0, 15, 247, 156, 108, 207, 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