Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abbdd6f336cc3e9325ff9f1c6c55a79bea424ffe97afb763f3895f31cfe9aa0b

Tx prefix hash: 5beee1a8acfd93f555c6c9c12abca38007a77648791d90c4e6716785d39c3bb6
Tx public key: 9388ae5a2d8c0afc65227a94c8530250c49c371cd3e94a9b039ff4b9e6baf7a7
Timestamp: 1719020874 Timestamp [UCT]: 2024-06-22 01:47:54 Age [y:d:h:m:s]: 00:311:12:03:08
Block: 1049430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222631 RingCT/type: yes/0
Extra: 019388ae5a2d8c0afc65227a94c8530250c49c371cd3e94a9b039ff4b9e6baf7a702110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4602324e4728a5ffb38b0ab3abadf7bfd5bf2a1c3402299a2d4c056a5cd5c9e6 0.600000000000 1519529 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": 1049440, "vin": [ { "gen": { "height": 1049430 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4602324e4728a5ffb38b0ab3abadf7bfd5bf2a1c3402299a2d4c056a5cd5c9e6" } } ], "extra": [ 1, 147, 136, 174, 90, 45, 140, 10, 252, 101, 34, 122, 148, 200, 83, 2, 80, 196, 156, 55, 28, 211, 233, 74, 155, 3, 159, 244, 185, 230, 186, 247, 167, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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