Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f262211e8cf3d9a78e80c8e1e95c37f716c6a5bb764c971d19ea51c82c2f82fb

Tx prefix hash: 96616230b27a3e2d7d6eb46f8b5777d1f72c429bd91f41e70a51b5002047f539
Tx public key: cb3e7c52fb67dfa4edf529ac151b35d48bea0979e096d291c82e0f6724f8d6ab
Timestamp: 1687750057 Timestamp [UCT]: 2023-06-26 03:27:37 Age [y:d:h:m:s]: 01:244:10:57:31
Block: 790454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 435818 RingCT/type: yes/0
Extra: 01cb3e7c52fb67dfa4edf529ac151b35d48bea0979e096d291c82e0f6724f8d6ab02110000000175e3f0e9000000000000000000

1 output(s) for total of 1.475359674000 dcy

stealth address amount amount idx
00: 05d0b18ca464828899fe5bdc4a02319eb5d878cf690518523d6157121fa665db 1.475359674000 1240799 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": 790464, "vin": [ { "gen": { "height": 790454 } } ], "vout": [ { "amount": 1475359674, "target": { "key": "05d0b18ca464828899fe5bdc4a02319eb5d878cf690518523d6157121fa665db" } } ], "extra": [ 1, 203, 62, 124, 82, 251, 103, 223, 164, 237, 245, 41, 172, 21, 27, 53, 212, 139, 234, 9, 121, 224, 150, 210, 145, 200, 46, 15, 103, 36, 248, 214, 171, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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