Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e69a56e39b668567a65056759f8388069ba40ae6dec6a029ff627a523ae8cf40

Tx prefix hash: 0026984f5582b73771307fd7a149444e3a2844c4c6dd78e90dc1ecc0ec28bf52
Tx public key: ce66fde9c8ae375cba75669c99cac73f8810a2b53e42774fd6cf42d63ae547cb
Timestamp: 1681620686 Timestamp [UCT]: 2023-04-16 04:51:26 Age [y:d:h:m:s]: 01:358:04:18:01
Block: 739605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 517268 RingCT/type: yes/0
Extra: 01ce66fde9c8ae375cba75669c99cac73f8810a2b53e42774fd6cf42d63ae547cb0211000000035029cbac000000000000000000

1 output(s) for total of 2.174612243000 dcy

stealth address amount amount idx
00: b7dcd96fc6eb5d7659cb7bfc8da726bb7ea6446fb401106c637e0038698e7fc0 2.174612243000 1186466 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": 739615, "vin": [ { "gen": { "height": 739605 } } ], "vout": [ { "amount": 2174612243, "target": { "key": "b7dcd96fc6eb5d7659cb7bfc8da726bb7ea6446fb401106c637e0038698e7fc0" } } ], "extra": [ 1, 206, 102, 253, 233, 200, 174, 55, 92, 186, 117, 102, 156, 153, 202, 199, 63, 136, 16, 162, 181, 62, 66, 119, 79, 214, 207, 66, 214, 58, 229, 71, 203, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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