Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01276658f86e458a943b9578236e1a3b7b319cf07b449e3d8c63297e0488cda9

Tx prefix hash: 79823865fc1da27ab9e276ab69eb495379884651526d63de359ffdcb3970fb46
Tx public key: 97d12f09b0cbc20f53f937d2c3976eba8682386f9bc7c33c0140eaac4e3f09a9
Timestamp: 1763975759 Timestamp [UCT]: 2025-11-24 09:15:59 Age [y:d:h:m:s]: 00:003:02:11:33
Block: 1419006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2219 RingCT/type: yes/0
Extra: 0197d12f09b0cbc20f53f937d2c3976eba8682386f9bc7c33c0140eaac4e3f09a902110000000417b19132000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d465a5b1d91471ac5649e84699da9aa8f49530b041bd01c1d0c52313aab6174 0.600000000000 1907539 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": 1419016, "vin": [ { "gen": { "height": 1419006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d465a5b1d91471ac5649e84699da9aa8f49530b041bd01c1d0c52313aab6174" } } ], "extra": [ 1, 151, 209, 47, 9, 176, 203, 194, 15, 83, 249, 55, 210, 195, 151, 110, 186, 134, 130, 56, 111, 155, 199, 195, 60, 1, 64, 234, 172, 78, 63, 9, 169, 2, 17, 0, 0, 0, 4, 23, 177, 145, 50, 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