Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a038f577b4cc87648ed59db3512731ff3c11fb91b584ddcf83204e28142cf0a

Tx prefix hash: 07002a04262c733a510bbc7056a3a9a40ca247ad080d34df78c43f9a8aad8918
Tx public key: d5e3f168ad7aa05f56afe217f8f2cd8b2011a3d92b0906a7fa279d316089c944
Timestamp: 1746573813 Timestamp [UTC]: 2025-05-06 23:23:33 Age [y:d:h:m:s]: 01:198:09:51:59
Block: 1277337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405968 RingCT/type: yes/0
Extra: 01d5e3f168ad7aa05f56afe217f8f2cd8b2011a3d92b0906a7fa279d316089c9440211000000031f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 409dac1de4457da25b0ebc9c233434e6cd9ecd874355fd96665fe5872acb1e0c 0.000600000000 1764692 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": 1277347, "vin": [ { "gen": { "height": 1277337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "409dac1de4457da25b0ebc9c233434e6cd9ecd874355fd96665fe5872acb1e0c" } } ], "extra": [ 1, 213, 227, 241, 104, 173, 122, 160, 95, 86, 175, 226, 23, 248, 242, 205, 139, 32, 17, 163, 217, 43, 9, 6, 167, 250, 39, 157, 49, 96, 137, 201, 68, 2, 17, 0, 0, 0, 3, 31, 144, 81, 122, 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: