Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9f0d53e4eeea0faa0a77e650442c5ecf0797950d6e0e128384a14d1d6268277

Tx prefix hash: 3d7e5ec2d62af5abbf41a8170d68643faf3c3507123de70ecbfc3d3e04ad0d92
Tx public key: ad322f1316b1570c2ae1ba9c0677169aa712713c85de3cbe4fdd9516a438294a
Timestamp: 1715127002 Timestamp [UCT]: 2024-05-08 00:10:02 Age [y:d:h:m:s]: 00:136:11:20:18
Block: 1017158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97753 RingCT/type: yes/0
Extra: 01ad322f1316b1570c2ae1ba9c0677169aa712713c85de3cbe4fdd9516a438294a0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0acbd45ee40df5d57dc1365fc952a4a2f34235e8ab9f35513f953019646ad89d 0.600000000000 1480925 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": 1017168, "vin": [ { "gen": { "height": 1017158 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0acbd45ee40df5d57dc1365fc952a4a2f34235e8ab9f35513f953019646ad89d" } } ], "extra": [ 1, 173, 50, 47, 19, 22, 177, 87, 12, 42, 225, 186, 156, 6, 119, 22, 154, 167, 18, 113, 60, 133, 222, 60, 190, 79, 221, 149, 22, 164, 56, 41, 74, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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