Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ae97288e2344c89ead2ab4cc5e408c4848eb1f14abf6bb741b500cafcf92984

Tx prefix hash: 0c6a9c2cab18217858e29f3976b7a2d7c16a2d9851c465a711b7bdbb8a4a33fd
Tx public key: 9ccbb319cbc9dd5f6d10433da398a463ce4db9d920d5136a47e42ea28de0e54a
Timestamp: 1671629915 Timestamp [UCT]: 2022-12-21 13:38:35 Age [y:d:h:m:s]: 02:132:10:46:07
Block: 657428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 616366 RingCT/type: yes/0
Extra: 019ccbb319cbc9dd5f6d10433da398a463ce4db9d920d5136a47e42ea28de0e54a021100000001e6d27f9c000000000000000000

1 output(s) for total of 4.070690656000 dcy

stealth address amount amount idx
00: 59a0473f0f84d2dff44a9dbc19aa3b4569eba7143599cbbf59a9119c2b1fcab5 4.070690656000 1098073 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": 657438, "vin": [ { "gen": { "height": 657428 } } ], "vout": [ { "amount": 4070690656, "target": { "key": "59a0473f0f84d2dff44a9dbc19aa3b4569eba7143599cbbf59a9119c2b1fcab5" } } ], "extra": [ 1, 156, 203, 179, 25, 203, 201, 221, 95, 109, 16, 67, 61, 163, 152, 164, 99, 206, 77, 185, 217, 32, 213, 19, 106, 71, 228, 46, 162, 141, 224, 229, 74, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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