Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed57dfd41b2c7eceb15b0cf128912e0548ac6a79d8d33c731c444e5c250a4b82

Tx prefix hash: 120a95cac52becd0b57136b10d68eb31eeefaf1c2a160100efa52905e2638e6b
Tx public key: c04789dfb0f7d4ad443c4ee1df56809c3798fb2235ac7c2a1ca0d8426146a547
Timestamp: 1763147149 Timestamp [UCT]: 2025-11-14 19:05:49 Age [y:d:h:m:s]: 00:043:09:42:57
Block: 1412141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31083 RingCT/type: yes/0
Extra: 01c04789dfb0f7d4ad443c4ee1df56809c3798fb2235ac7c2a1ca0d8426146a547021100000009e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29e4f2565add107133f0301a360c89e269461fbcee20a26d7fea1532f5e42bc7 0.600000000000 1900608 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": 1412151, "vin": [ { "gen": { "height": 1412141 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29e4f2565add107133f0301a360c89e269461fbcee20a26d7fea1532f5e42bc7" } } ], "extra": [ 1, 192, 71, 137, 223, 176, 247, 212, 173, 68, 60, 78, 225, 223, 86, 128, 156, 55, 152, 251, 34, 53, 172, 124, 42, 28, 160, 216, 66, 97, 70, 165, 71, 2, 17, 0, 0, 0, 9, 228, 220, 144, 9, 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