Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a1227712b8d9f208e00f37acaa41d8823376d50371112d2047a851a3ab733ee

Tx prefix hash: 36f4b50200f9744054af13910358d5e71a3ba367cb7fed91116f6a70f47e135f
Tx public key: 547dd489b4c3ff63fb1bbd27c9c86d0a2508e6c04ab2e7df1c1403045d02a68e
Timestamp: 1737482584 Timestamp [UCT]: 2025-01-21 18:03:04 Age [y:d:h:m:s]: 00:147:03:44:42
Block: 1202291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104920 RingCT/type: yes/0
Extra: 01547dd489b4c3ff63fb1bbd27c9c86d0a2508e6c04ab2e7df1c1403045d02a68e0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c88fd224fc95030459a4eeb6078b0bf306ea0e336eff65f37a833a14286bd98 0.600000000000 1688954 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": 1202301, "vin": [ { "gen": { "height": 1202291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c88fd224fc95030459a4eeb6078b0bf306ea0e336eff65f37a833a14286bd98" } } ], "extra": [ 1, 84, 125, 212, 137, 180, 195, 255, 99, 251, 27, 189, 39, 201, 200, 109, 10, 37, 8, 230, 192, 74, 178, 231, 223, 28, 20, 3, 4, 93, 2, 166, 142, 2, 17, 0, 0, 0, 4, 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