Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6ff27e01f75233b20b0912a584ecaf264335ef321c17843e70c6fc0e28c4719

Tx prefix hash: bbd14680c5adf19a5f48d1ecd3bdeccda52e7639f1bd41583b3554a2f3f4f35b
Tx public key: 979e1881dcdf4ed7227b5e266e917098370f7f3c9dd617018503d45f6bdf496c
Timestamp: 1716906295 Timestamp [UCT]: 2024-05-28 14:24:55 Age [y:d:h:m:s]: 00:339:18:07:38
Block: 1031917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242840 RingCT/type: yes/0
Extra: 01979e1881dcdf4ed7227b5e266e917098370f7f3c9dd617018503d45f6bdf496c02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb7e4149e40d1a9a7125bf032e06ca23c7f6f84f30f7360e1beec66685dcb011 0.600000000000 1500366 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": 1031927, "vin": [ { "gen": { "height": 1031917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb7e4149e40d1a9a7125bf032e06ca23c7f6f84f30f7360e1beec66685dcb011" } } ], "extra": [ 1, 151, 158, 24, 129, 220, 223, 78, 215, 34, 123, 94, 38, 110, 145, 112, 152, 55, 15, 127, 60, 157, 214, 23, 1, 133, 3, 212, 95, 107, 223, 73, 108, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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