Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5389b06a4d9647cca4381b930006d301c83f2bf0e26722937a853f9c5ff1da0a

Tx prefix hash: 666e305a41496f61930c27ad509fb2e42cb77ab1ad81310d22b8a17d3aacb891
Tx public key: f610cbe76316638b3b48279c3805c72e8721a2ec6eda9789916be693b4b85d79
Timestamp: 1736237325 Timestamp [UCT]: 2025-01-07 08:08:45 Age [y:d:h:m:s]: 00:362:15:21:47
Block: 1192044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256763 RingCT/type: yes/0
Extra: 01f610cbe76316638b3b48279c3805c72e8721a2ec6eda9789916be693b4b85d790211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0789b44cda9147f1b8d2e5a8139ed69a41d007dc411bf4cee4e748c1a38e58b4 0.600000000000 1678589 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": 1192054, "vin": [ { "gen": { "height": 1192044 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0789b44cda9147f1b8d2e5a8139ed69a41d007dc411bf4cee4e748c1a38e58b4" } } ], "extra": [ 1, 246, 16, 203, 231, 99, 22, 99, 139, 59, 72, 39, 156, 56, 5, 199, 46, 135, 33, 162, 236, 110, 218, 151, 137, 145, 107, 230, 147, 180, 184, 93, 121, 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