Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e9b1d68588a8a4a7a9ea00d49ec83c0a6261f093c6d05ca91f69249994d1aa8

Tx prefix hash: 5515d2f5a9be8627f26bcbc5b7f0789f5ad80426f8f0928f26d1c639e5f9d6c4
Tx public key: ff4c84368db85fc9f029f856c0680144b9046729488fc90d53aa9e33e485eed6
Timestamp: 1733723940 Timestamp [UCT]: 2024-12-09 05:59:00 Age [y:d:h:m:s]: 00:125:10:57:48
Block: 1171235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89468 RingCT/type: yes/0
Extra: 01ff4c84368db85fc9f029f856c0680144b9046729488fc90d53aa9e33e485eed60211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa7b2d5816dbfff7c524ef18664bcad18d47642af6fd17c74d56511abf130503 0.600000000000 1656974 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": 1171245, "vin": [ { "gen": { "height": 1171235 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa7b2d5816dbfff7c524ef18664bcad18d47642af6fd17c74d56511abf130503" } } ], "extra": [ 1, 255, 76, 132, 54, 141, 184, 95, 201, 240, 41, 248, 86, 192, 104, 1, 68, 185, 4, 103, 41, 72, 143, 201, 13, 83, 170, 158, 51, 228, 133, 238, 214, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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