Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d95dfd9d6d6c937af672c2859c3395ebeec554fce4e9a9ea732acc9af1d1d493

Tx prefix hash: 0d159528b2354aec27dbef5d99e97523181a2a809bf33a41ea201df6c05264d4
Tx public key: b6355690cbbe126aa95edf7c49050f49c148b8dc9fb7d7b0662efe16b8f83918
Timestamp: 1750212508 Timestamp [UTC]: 2025-06-18 02:08:28 Age [y:d:h:m:s]: 01:154:10:45:56
Block: 1307346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374549 RingCT/type: yes/0
Extra: 01b6355690cbbe126aa95edf7c49050f49c148b8dc9fb7d7b0662efe16b8f83918021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 21a30fc7592f4f89a316b791448eafb2d54fb89bab6b211a1d358feafcbf1bf1 0.000600000000 1794957 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": 1307356, "vin": [ { "gen": { "height": 1307346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21a30fc7592f4f89a316b791448eafb2d54fb89bab6b211a1d358feafcbf1bf1" } } ], "extra": [ 1, 182, 53, 86, 144, 203, 190, 18, 106, 169, 94, 223, 124, 73, 5, 15, 73, 193, 72, 184, 220, 159, 183, 215, 176, 102, 46, 254, 22, 184, 248, 57, 24, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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: