Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee76501bd9ab6667263579f92dece5d726a00f5a63707ac64a6401062a5fb11d

Tx prefix hash: e2d373df0c4eb79eacec458e67ec402d8124f77c7b8b391a8cb4161d0ea7d569
Tx public key: 50e8c4e5b4106fc2147ee5a0f6ee4597b0cf3b13f2746f09ce5e1d657cf583b6
Timestamp: 1764932703 Timestamp [UCT]: 2025-12-05 11:05:03 Age [y:d:h:m:s]: 00:018:06:34:47
Block: 1426947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13065 RingCT/type: yes/0
Extra: 0150e8c4e5b4106fc2147ee5a0f6ee4597b0cf3b13f2746f09ce5e1d657cf583b602110000000770609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92720c99774d88def462a6207f9bb8c7279b66ae7bf44202fd19b830572289be 0.600000000000 1915642 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": 1426957, "vin": [ { "gen": { "height": 1426947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92720c99774d88def462a6207f9bb8c7279b66ae7bf44202fd19b830572289be" } } ], "extra": [ 1, 80, 232, 196, 229, 180, 16, 111, 194, 20, 126, 229, 160, 246, 238, 69, 151, 176, 207, 59, 19, 242, 116, 111, 9, 206, 94, 29, 101, 124, 245, 131, 182, 2, 17, 0, 0, 0, 7, 112, 96, 157, 3, 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