Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c39c9d941b953d6dc675e11956b5ad4cc3fdb16e9ad0434d1ad4dbed58c4b0a

Tx prefix hash: 443c6796f98acf27e2b55cfb0136012a708a7ca72795f35a7576a9aaabb7374f
Tx public key: 4a602e9ed84c52cda72760ba9efb1f268dae2224ccb9870944665f964f96cac0
Timestamp: 1726485609 Timestamp [UCT]: 2024-09-16 11:20:09 Age [y:d:h:m:s]: 01:054:03:06:18
Block: 1111323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297096 RingCT/type: yes/0
Extra: 014a602e9ed84c52cda72760ba9efb1f268dae2224ccb9870944665f964f96cac0021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66fd5f9c22bdaa85eb280015ddcdbd3178935bdf6c6527ce396bf53f1fa667d6 0.600000000000 1590242 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": 1111333, "vin": [ { "gen": { "height": 1111323 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66fd5f9c22bdaa85eb280015ddcdbd3178935bdf6c6527ce396bf53f1fa667d6" } } ], "extra": [ 1, 74, 96, 46, 158, 216, 76, 82, 205, 167, 39, 96, 186, 158, 251, 31, 38, 141, 174, 34, 36, 204, 185, 135, 9, 68, 102, 95, 150, 79, 150, 202, 192, 2, 17, 0, 0, 0, 7, 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