Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a6198c7ffae668ee2c83a7dd0ecf0e7493050669fe2ca77e1e9c607bec65dce

Tx prefix hash: 300bfee91e81d1818034f40bdf91a22bab706939f12e5fb6784cf681d1d157e7
Tx public key: 62644682d071dbd2e908e85817d28e2cebbc92f43a4a9076abb96efc7ec0c0d8
Timestamp: 1731168937 Timestamp [UTC]: 2024-11-09 16:15:37 Age [y:d:h:m:s]: 02:006:07:24:43
Block: 1150072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 529171 RingCT/type: yes/0
Extra: 0162644682d071dbd2e908e85817d28e2cebbc92f43a4a9076abb96efc7ec0c0d8021100000001a11dba98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7656067f1b29a9229ab2ed65528c53fb9152d965bdb6402625bf882e13fd7014 0.000600000000 1635273 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 dinastycoin-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": 1150082, "vin": [ { "gen": { "height": 1150072 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7656067f1b29a9229ab2ed65528c53fb9152d965bdb6402625bf882e13fd7014" } } ], "extra": [ 1, 98, 100, 70, 130, 208, 113, 219, 210, 233, 8, 232, 88, 23, 210, 142, 44, 235, 188, 146, 244, 58, 74, 144, 118, 171, 185, 110, 252, 126, 192, 192, 216, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: