Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd1dc44a02e83108f8192b54efa66efac9aa2027bc9936c91a0c9227f08035be

Tx prefix hash: 321eb2f24dc4eea8d7747a7e2f23c49cb53cc7d82ea737b7e66701b470229166
Tx public key: 5bbd13eb7ff04114411a37bfce8c94be2aa561d7441e060e249ad235c0718957
Timestamp: 1745525231 Timestamp [UCT]: 2025-04-24 20:07:11 Age [y:d:h:m:s]: 00:020:08:00:46
Block: 1268658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14543 RingCT/type: yes/0
Extra: 015bbd13eb7ff04114411a37bfce8c94be2aa561d7441e060e249ad235c0718957021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: edd6ebe402c73db8921d56d8b49d751c8e5e7569f3be47cfbda8d5ef322ae8fd 0.600000000000 1755889 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": 1268668, "vin": [ { "gen": { "height": 1268658 } } ], "vout": [ { "amount": 600000000, "target": { "key": "edd6ebe402c73db8921d56d8b49d751c8e5e7569f3be47cfbda8d5ef322ae8fd" } } ], "extra": [ 1, 91, 189, 19, 235, 127, 240, 65, 20, 65, 26, 55, 191, 206, 140, 148, 190, 42, 165, 97, 215, 68, 30, 6, 14, 36, 154, 210, 53, 192, 113, 137, 87, 2, 17, 0, 0, 0, 1, 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