Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6eeaab0bc3a8a594dcb52737289101e127b6b0ddd2bee81d92a655531b4b0c5

Tx prefix hash: eb83abc260682bcf365b49bae59d9deee10fd1c4049be4165e9a74d86a56c97a
Tx public key: 571cdd7144fdd068314b32c927202c5510a5071bc4e48de2a87544b1c8f2701a
Timestamp: 1716829183 Timestamp [UCT]: 2024-05-27 16:59:43 Age [y:d:h:m:s]: 00:304:13:41:03
Block: 1031281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217659 RingCT/type: yes/0
Extra: 01571cdd7144fdd068314b32c927202c5510a5071bc4e48de2a87544b1c8f2701a0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71124b194a3a6600b5cf0d5c9d0eafc85ccf3be96ede20e686f050623358e4b8 0.600000000000 1499694 of 15

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": 1031291, "vin": [ { "gen": { "height": 1031281 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71124b194a3a6600b5cf0d5c9d0eafc85ccf3be96ede20e686f050623358e4b8" } } ], "extra": [ 1, 87, 28, 221, 113, 68, 253, 208, 104, 49, 75, 50, 201, 39, 32, 44, 85, 16, 165, 7, 27, 196, 228, 141, 226, 168, 117, 68, 177, 200, 242, 112, 26, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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