Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d305c0b7a9d70ee16716628b362e34a03b40da7bcc809b6fa3149c8b13d8710

Tx prefix hash: c680a981e6a549188f159b208aabf15b5f034e02d999891d4951d74812298115
Tx public key: d7a98ee9977fd721259c307c6f5d49cee93f052f3674beaeec80b1f80613dcb5
Timestamp: 1766477385 Timestamp [UCT]: 2025-12-23 08:09:45 Age [y:d:h:m:s]: 00:008:11:22:37
Block: 1439737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6075 RingCT/type: yes/0
Extra: 01d7a98ee9977fd721259c307c6f5d49cee93f052f3674beaeec80b1f80613dcb5021100000005d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08652421757325fdedb76a10702cfd17fb6855aad90969d60aa941751313a83f 0.600000000000 1928584 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": 1439747, "vin": [ { "gen": { "height": 1439737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08652421757325fdedb76a10702cfd17fb6855aad90969d60aa941751313a83f" } } ], "extra": [ 1, 215, 169, 142, 233, 151, 127, 215, 33, 37, 156, 48, 124, 111, 93, 73, 206, 233, 63, 5, 47, 54, 116, 190, 174, 236, 128, 177, 248, 6, 19, 220, 181, 2, 17, 0, 0, 0, 5, 214, 225, 157, 124, 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