Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa7e52f36751988ba1200ca6a51b14269d77779aabc87fa849e64bf166ff6916

Tx prefix hash: 852e09365054414d2125c7e04d7dc4dc6888ee4ed6bd0483927ff1c9209d3e1c
Tx public key: b70d563f0e86e761aa2b308d11b577952180719dfaac669e59596cc36cceaea5
Timestamp: 1751438920 Timestamp [UCT]: 2025-07-02 06:48:40 Age [y:d:h:m:s]: 00:135:17:58:02
Block: 1317051 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95261 RingCT/type: yes/0
Extra: 01b70d563f0e86e761aa2b308d11b577952180719dfaac669e59596cc36cceaea502110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a4bb73dc7647499e5b02d2fda454dea8f28b1aa9c97706872c762d874a01dc7 0.600000000000 1804716 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": 1317061, "vin": [ { "gen": { "height": 1317051 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a4bb73dc7647499e5b02d2fda454dea8f28b1aa9c97706872c762d874a01dc7" } } ], "extra": [ 1, 183, 13, 86, 63, 14, 134, 231, 97, 170, 43, 48, 141, 17, 181, 119, 149, 33, 128, 113, 157, 250, 172, 102, 158, 89, 89, 108, 195, 108, 206, 174, 165, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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