Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f5e1500ddf2801c7dea621680e658731eef445dd2be910e448ba6dc3d5774fa

Tx prefix hash: 0ddf79da452cc68846bc984bca10d4a8b0649ec94e2ab0991ba92d9e5a84f42a
Tx public key: 4c6a0fe081a99dcd472b2457197ee3e5e09937c38ae772559d7bd4d4b83a6755
Timestamp: 1722904967 Timestamp [UCT]: 2024-08-06 00:42:47 Age [y:d:h:m:s]: 01:093:21:42:58
Block: 1081634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325601 RingCT/type: yes/0
Extra: 014c6a0fe081a99dcd472b2457197ee3e5e09937c38ae772559d7bd4d4b83a6755021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30569a95dcef972db3f8f555d4d968b0391387d5abed9e6f0b028e76b8d559ee 0.600000000000 1555451 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": 1081644, "vin": [ { "gen": { "height": 1081634 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30569a95dcef972db3f8f555d4d968b0391387d5abed9e6f0b028e76b8d559ee" } } ], "extra": [ 1, 76, 106, 15, 224, 129, 169, 157, 205, 71, 43, 36, 87, 25, 126, 227, 229, 224, 153, 55, 195, 138, 231, 114, 85, 157, 123, 212, 212, 184, 58, 103, 85, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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