Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99a50cd6d325c69ffe9e499f70386d0dfcfbcb9063a106c311d031ce6498b0cc

Tx prefix hash: d866e609ea2148349912608eb2ac55bf03eb90fe2967842195646f1e0d97e8ce
Tx public key: 4136a5e6b6c3463ca59c9883cc8cf09750584652a74c5862e59d4e427424b793
Timestamp: 1715778292 Timestamp [UTC]: 2024-05-15 13:04:52 Age [y:d:h:m:s]: 02:191:10:01:37
Block: 1022560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 661590 RingCT/type: yes/0
Extra: 014136a5e6b6c3463ca59c9883cc8cf09750584652a74c5862e59d4e427424b79302110000000359dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1f7f80523c71c31d717c60a5ef337408a93b96a361cb0e8e6a48787b87e298ba 0.000600000000 1487199 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": 1022570, "vin": [ { "gen": { "height": 1022560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f7f80523c71c31d717c60a5ef337408a93b96a361cb0e8e6a48787b87e298ba" } } ], "extra": [ 1, 65, 54, 165, 230, 182, 195, 70, 60, 165, 156, 152, 131, 204, 140, 240, 151, 80, 88, 70, 82, 167, 76, 88, 98, 229, 157, 78, 66, 116, 36, 183, 147, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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: