Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86add73d3c448715bf6459e86c321e2bac7f49e966fd8748387118704a9ee8ce

Tx prefix hash: beaee5ff2179b698bd97372f6b5ef60d7e0d3d9a1b24da3f9ee672d0f100508a
Tx public key: 7947e546607e33775e0d53dd6784d141b8cdc55532376bf0ede6ff4a1f7f913e
Timestamp: 1754427418 Timestamp [UCT]: 2025-08-05 20:56:58 Age [y:d:h:m:s]: 00:011:21:31:47
Block: 1341019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7653 RingCT/type: yes/0
Extra: 017947e546607e33775e0d53dd6784d141b8cdc55532376bf0ede6ff4a1f7f913e021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b098513a407cdacc1e910e6a7f290330677d5e95e3f419f6e9a37dc36ed496b 0.600000000000 1828840 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": 1341029, "vin": [ { "gen": { "height": 1341019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b098513a407cdacc1e910e6a7f290330677d5e95e3f419f6e9a37dc36ed496b" } } ], "extra": [ 1, 121, 71, 229, 70, 96, 126, 51, 119, 94, 13, 83, 221, 103, 132, 209, 65, 184, 205, 197, 85, 50, 55, 107, 240, 237, 230, 255, 74, 31, 127, 145, 62, 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