Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5f4dac87f3d86cfa6fb5ac123bc5f1cbf9cb70368f690aaa18270fb7c0d48c4

Tx prefix hash: 6c34035f3841b47b4d9e1bacce525be8630d2bc9e3a1cb7aba12eca3fb3250bf
Tx public key: 566cd920960ac88c63dbe5ce98f93b95c82827cb7da51285919983dd1dd1d58a
Timestamp: 1763823549 Timestamp [UCT]: 2025-11-22 14:59:09 Age [y:d:h:m:s]: 00:036:22:08:56
Block: 1417741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26444 RingCT/type: yes/0
Extra: 01566cd920960ac88c63dbe5ce98f93b95c82827cb7da51285919983dd1dd1d58a021100000001fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 888301511c4362eec02a83c4aeb26ef69b2b48c56311ed0b020694f99db5b9aa 0.600000000000 1906268 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": 1417751, "vin": [ { "gen": { "height": 1417741 } } ], "vout": [ { "amount": 600000000, "target": { "key": "888301511c4362eec02a83c4aeb26ef69b2b48c56311ed0b020694f99db5b9aa" } } ], "extra": [ 1, 86, 108, 217, 32, 150, 10, 200, 140, 99, 219, 229, 206, 152, 249, 59, 149, 200, 40, 39, 203, 125, 165, 18, 133, 145, 153, 131, 221, 29, 209, 213, 138, 2, 17, 0, 0, 0, 1, 251, 143, 208, 137, 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