Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af9215f9e8d97efe973b2e65b95c5a75a7dc838900bff9f5c4ccfbb057740f7c

Tx prefix hash: 3c521045de194e3d36c6db042e84a41cb22e0a7e94fae79e91c60edaa8305086
Tx public key: 9cc8a534ca385a90041c775024efad88b178af52a4b250c98c243e43aeac38eb
Timestamp: 1700669170 Timestamp [UTC]: 2023-11-22 16:06:10 Age [y:d:h:m:s]: 02:171:15:41:21
Block: 897295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 634647 RingCT/type: yes/0
Extra: 019cc8a534ca385a90041c775024efad88b178af52a4b250c98c243e43aeac38eb02110000000bfaf35c9c000000000000000000

1 output(s) for total of 0.000652963894 xmr

stealth address amount amount idx tag
00: 701fd3a6e8a2066a817ac3c68b50981544e2e9eba7985bf20decbd2027eb3c6d 0.000652963894 1353668 of 0 -

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": 897305, "vin": [ { "gen": { "height": 897295 } } ], "vout": [ { "amount": 652963894, "target": { "key": "701fd3a6e8a2066a817ac3c68b50981544e2e9eba7985bf20decbd2027eb3c6d" } } ], "extra": [ 1, 156, 200, 165, 52, 202, 56, 90, 144, 4, 28, 119, 80, 36, 239, 173, 136, 177, 120, 175, 82, 164, 178, 80, 201, 140, 36, 62, 67, 174, 172, 56, 235, 2, 17, 0, 0, 0, 11, 250, 243, 92, 156, 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: