Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16e2c275567bbf681cbf1f78e4d80123d2b76259deac7dd18e506fbdb04af0fa

Tx prefix hash: 0a950527f9a0f2d3d1cc4fd185743a5c4090f9f1afc768bbb0d77bd6e09c681e
Tx public key: 96e8d6ced2b47502d9776251124de755243bfbca398102b835d334f89181a179
Timestamp: 1750299498 Timestamp [UTC]: 2025-06-19 02:18:18 Age [y:d:h:m:s]: 01:151:12:14:05
Block: 1308048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372393 RingCT/type: yes/0
Extra: 0196e8d6ced2b47502d9776251124de755243bfbca398102b835d334f89181a1790211000000022609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a271c91c4e6737993dd365ace56da8725eb7c3ee45f732c3e002c6d65b03082b 0.000600000000 1795661 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": 1308058, "vin": [ { "gen": { "height": 1308048 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a271c91c4e6737993dd365ace56da8725eb7c3ee45f732c3e002c6d65b03082b" } } ], "extra": [ 1, 150, 232, 214, 206, 210, 180, 117, 2, 217, 119, 98, 81, 18, 77, 231, 85, 36, 59, 251, 202, 57, 129, 2, 184, 53, 211, 52, 248, 145, 129, 161, 121, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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: