Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9a0f3645b7a1b88e7b84de86776883ebdd61d80f869e9238dacc0ea9594207b

Tx prefix hash: 534eaea41e4a2125fd2ad5ecac91e541344f576a0a85e2d6b41ec1c7b680f3d4
Tx public key: a58c3b91bb34dfd91cb403220860cf40b150cdb2fb2dac881011fbfc5dbb965f
Timestamp: 1762322758 Timestamp [UCT]: 2025-11-05 06:05:58 Age [y:d:h:m:s]: 00:089:07:05:28
Block: 1405304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63761 RingCT/type: yes/0
Extra: 01a58c3b91bb34dfd91cb403220860cf40b150cdb2fb2dac881011fbfc5dbb965f021100000001df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8df8ae7c1c07a90ce6aae978ded0a6919cc332594f5bf6c1487ae0c9e556c481 0.600000000000 1893675 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": 1405314, "vin": [ { "gen": { "height": 1405304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8df8ae7c1c07a90ce6aae978ded0a6919cc332594f5bf6c1487ae0c9e556c481" } } ], "extra": [ 1, 165, 140, 59, 145, 187, 52, 223, 217, 28, 180, 3, 34, 8, 96, 207, 64, 177, 80, 205, 178, 251, 45, 172, 136, 16, 17, 251, 252, 93, 187, 150, 95, 2, 17, 0, 0, 0, 1, 223, 90, 36, 122, 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