Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81cf01df4f1af1f879ed14dbc9269200100243cd94c027978a68d3ad03896bcc

Tx prefix hash: 70219797c874c7c24824db913fa9a177768e81cc2c6c49f433cf6605788d7275
Tx public key: 5789aa6d01a93612e7e5e5e77185d2323cb80283fe09e6c69e98f6f74ff10d3c
Timestamp: 1738713684 Timestamp [UCT]: 2025-02-05 00:01:24 Age [y:d:h:m:s]: 00:335:02:05:49
Block: 1212260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237329 RingCT/type: yes/0
Extra: 015789aa6d01a93612e7e5e5e77185d2323cb80283fe09e6c69e98f6f74ff10d3c021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fd756abf158a5bd5854511dbb5a015d02ba2f570519216e596802a587f38387 0.600000000000 1699031 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": 1212270, "vin": [ { "gen": { "height": 1212260 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fd756abf158a5bd5854511dbb5a015d02ba2f570519216e596802a587f38387" } } ], "extra": [ 1, 87, 137, 170, 109, 1, 169, 54, 18, 231, 229, 229, 231, 113, 133, 210, 50, 60, 184, 2, 131, 254, 9, 230, 198, 158, 152, 246, 247, 79, 241, 13, 60, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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