Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 110f2e7cff605c0577fe07c5b97ccaf1755a5fd06e2ed12df98891013f2a5cd8

Tx prefix hash: 4dfb8236b855ef0852427d3f546822e10be9ac6dfebaf2c9b10140b4d0a4fc5d
Tx public key: ec23fa506fe8aa146140a5a761d6a71a285647be8ca0123a7efbdac49bf9e701
Timestamp: 1749883570 Timestamp [UCT]: 2025-06-14 06:46:10 Age [y:d:h:m:s]: 00:157:20:09:53
Block: 1304668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110569 RingCT/type: yes/0
Extra: 01ec23fa506fe8aa146140a5a761d6a71a285647be8ca0123a7efbdac49bf9e701021100000010bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2fd6d48771138bbcc440e3a1dbb21926fdfad45f1eb2496fdfd793636a3a3ff1 0.600000000000 1792259 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": 1304678, "vin": [ { "gen": { "height": 1304668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fd6d48771138bbcc440e3a1dbb21926fdfad45f1eb2496fdfd793636a3a3ff1" } } ], "extra": [ 1, 236, 35, 250, 80, 111, 232, 170, 20, 97, 64, 165, 167, 97, 214, 167, 26, 40, 86, 71, 190, 140, 160, 18, 58, 126, 251, 218, 196, 155, 249, 231, 1, 2, 17, 0, 0, 0, 16, 191, 81, 178, 162, 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