Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd9a25ed24ed35b291b46daef1593375617378097b108f6d43eb7dfac61b7c9e

Tx prefix hash: 7c4578943d47d0ea9943a134eff712546e0785cf9322cc528ccc99fb666d2e0f
Tx public key: ae06563097ad10c270cf46a4625a29b802b7cf1e41adc16f7e554d0f98e1bf99
Timestamp: 1763777342 Timestamp [UCT]: 2025-11-22 02:09:02 Age [y:d:h:m:s]: 00:005:10:57:06
Block: 1417351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 3923 RingCT/type: yes/0
Extra: 01ae06563097ad10c270cf46a4625a29b802b7cf1e41adc16f7e554d0f98e1bf990208b8cf3de7dbb41aa2

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25c415feef051f245b2f6f0e749c35c47b64fb54cb258f9b44ef4260c7e3ff43 0.600000000000 1905874 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": 1417361, "vin": [ { "gen": { "height": 1417351 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25c415feef051f245b2f6f0e749c35c47b64fb54cb258f9b44ef4260c7e3ff43" } } ], "extra": [ 1, 174, 6, 86, 48, 151, 173, 16, 194, 112, 207, 70, 164, 98, 90, 41, 184, 2, 183, 207, 30, 65, 173, 193, 111, 126, 85, 77, 15, 152, 225, 191, 153, 2, 8, 184, 207, 61, 231, 219, 180, 26, 162 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8