Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e57f9ecc1f1189d41eea3aed6af6e48b277dd07a742befdc6695823b091bbed

Tx prefix hash: c7296c2b0d3353672519f451d57d6035d798a10068b7f4fd8a1dfb51e33a4345
Tx public key: dca26a1e872f09ed8a4b57f9a6287538db48f3a143ebedcd3d4ec01f089c6f0b
Timestamp: 1674614201 Timestamp [UCT]: 2023-01-25 02:36:41 Age [y:d:h:m:s]: 02:035:14:43:13
Block: 682167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 547060 RingCT/type: yes/0
Extra: 01dca26a1e872f09ed8a4b57f9a6287538db48f3a143ebedcd3d4ec01f089c6f0b0211000000045029cbac000000000000000000

1 output(s) for total of 3.370524493000 dcy

stealth address amount amount idx
00: 01c0743245637bbfe5a4a9f089a1e2899ba5cb95a6c0bfbb8b642e5ae29edcd7 3.370524493000 1124282 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": 682177, "vin": [ { "gen": { "height": 682167 } } ], "vout": [ { "amount": 3370524493, "target": { "key": "01c0743245637bbfe5a4a9f089a1e2899ba5cb95a6c0bfbb8b642e5ae29edcd7" } } ], "extra": [ 1, 220, 162, 106, 30, 135, 47, 9, 237, 138, 75, 87, 249, 166, 40, 117, 56, 219, 72, 243, 161, 67, 235, 237, 205, 61, 78, 192, 31, 8, 156, 111, 11, 2, 17, 0, 0, 0, 4, 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