Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f45b4a884d9d729924cd2cd7d66a51108835e558e2197d6918b0bcc3eed54f9

Tx prefix hash: 703347ae593b9f35ac797875f1fcbc1e39c461f1410e83d00f4238d5dc394443
Tx public key: 54940d3aacddecbe45f355ea6a7295ed9c475458c0c60dcbc16e45810a5ce9cf
Timestamp: 1745184064 Timestamp [UTC]: 2025-04-20 21:21:04 Age [y:d:h:m:s]: 01:026:17:18:03
Block: 1265825 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270122 RingCT/type: yes/0
Extra: 0154940d3aacddecbe45f355ea6a7295ed9c475458c0c60dcbc16e45810a5ce9cf02110000001cdbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ab340567830567bd1ab64b6072708caef056c2068064d840aa8630b396290124 0.000600000000 1753038 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": 1265835, "vin": [ { "gen": { "height": 1265825 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab340567830567bd1ab64b6072708caef056c2068064d840aa8630b396290124" } } ], "extra": [ 1, 84, 148, 13, 58, 172, 221, 236, 190, 69, 243, 85, 234, 106, 114, 149, 237, 156, 71, 84, 88, 192, 198, 13, 203, 193, 110, 69, 129, 10, 92, 233, 207, 2, 17, 0, 0, 0, 28, 219, 181, 113, 193, 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: