Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 808b64a5fb71a6939d4e76d143a246438d5c0ff79b77571915d649365db6434e

Tx prefix hash: 8442a3cecc50b63710e53c9db9b61a9f47230b9861d95a7776c43d6ecb132d56
Tx public key: 42fd526ff5f16aa24e9684405d02eac1f0697c1ce803f9c2945aa2f748025de9
Timestamp: 1742420481 Timestamp [UCT]: 2025-03-19 21:41:21 Age [y:d:h:m:s]: 00:259:05:06:40
Block: 1242981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182993 RingCT/type: yes/0
Extra: 0142fd526ff5f16aa24e9684405d02eac1f0697c1ce803f9c2945aa2f748025de9021100000002bfa77623000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d703b2703c1731c82b24f99ca3a4412c420b4242e86bae95a1077681089cdad 0.600000000000 1729964 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": 1242991, "vin": [ { "gen": { "height": 1242981 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d703b2703c1731c82b24f99ca3a4412c420b4242e86bae95a1077681089cdad" } } ], "extra": [ 1, 66, 253, 82, 111, 245, 241, 106, 162, 78, 150, 132, 64, 93, 2, 234, 193, 240, 105, 124, 28, 232, 3, 249, 194, 148, 90, 162, 247, 72, 2, 93, 233, 2, 17, 0, 0, 0, 2, 191, 167, 118, 35, 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