Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e876366edf003e785636e1e0bb35aa15a0dbf692df9bc84bc07a0d23aee2e282

Tx prefix hash: b691993329bc68c6ed9d9681109f59ae22eafdc581f04b28dc644c6cfdcfb227
Tx public key: 8e426ce36319d68a952d7c5d83005c021f8fa014711cd0466bafe4a96ed305bf
Timestamp: 1749912316 Timestamp [UCT]: 2025-06-14 14:45:16 Age [y:d:h:m:s]: 00:226:22:04:35
Block: 1304913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159841 RingCT/type: yes/0
Extra: 018e426ce36319d68a952d7c5d83005c021f8fa014711cd0466bafe4a96ed305bf021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c177670d3f2a9d8a156706f235c243a37d01b7406481c96c0d2d3c6f8a6bcf1 0.600000000000 1792508 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": 1304923, "vin": [ { "gen": { "height": 1304913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c177670d3f2a9d8a156706f235c243a37d01b7406481c96c0d2d3c6f8a6bcf1" } } ], "extra": [ 1, 142, 66, 108, 227, 99, 25, 214, 138, 149, 45, 124, 93, 131, 0, 92, 2, 31, 143, 160, 20, 113, 28, 208, 70, 107, 175, 228, 169, 110, 211, 5, 191, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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