Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89ed582443e39afbae138b0e9bdab9ba9d9092f2bec145fc56eeba23f4e3c854

Tx prefix hash: b1b4e9094a0ad5efca642f1cca6b362752bb9168718e35316472c00ce82d3e5e
Tx public key: d3aae893fa1726916de892385d816fa307fc00f8e235db8f1f63bf3336a7a08e
Timestamp: 1731736846 Timestamp [UCT]: 2024-11-16 06:00:46 Age [y:d:h:m:s]: 00:363:19:02:10
Block: 1154769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257551 RingCT/type: yes/0
Extra: 01d3aae893fa1726916de892385d816fa307fc00f8e235db8f1f63bf3336a7a08e021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6812b73eb8fe5d4d99e92a939f8cfd4237a4fc67f9a8c6a01de373f544fa605e 0.600000000000 1640382 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": 1154779, "vin": [ { "gen": { "height": 1154769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6812b73eb8fe5d4d99e92a939f8cfd4237a4fc67f9a8c6a01de373f544fa605e" } } ], "extra": [ 1, 211, 170, 232, 147, 250, 23, 38, 145, 109, 232, 146, 56, 93, 129, 111, 163, 7, 252, 0, 248, 226, 53, 219, 143, 31, 99, 191, 51, 54, 167, 160, 142, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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