Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae8731275ffc9f2bcaafb66f22d958e8319f8b836eb844cd8378f8e6ebbdfcd1

Tx prefix hash: 7656ab3416fb5e58327c44cc485eab15780891159b9c50aced8f3b842b04f51e
Tx public key: 63a9a143c96b8b07d06cb5e5f0dec9cece9ec135e51322d0463562373782828d
Timestamp: 1773901848 Timestamp [UTC]: 2026-03-19 06:30:48 Age [y:d:h:m:s]: 00:240:17:28:59
Block: 1501025 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177473 RingCT/type: yes/0
Extra: 0163a9a143c96b8b07d06cb5e5f0dec9cece9ec135e51322d0463562373782828d021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c4282656801173fadb5f5a449e499133cfe55ba7d766500308f2427d1963295d 0.000600000000 1990703 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": 1501035, "vin": [ { "gen": { "height": 1501025 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4282656801173fadb5f5a449e499133cfe55ba7d766500308f2427d1963295d" } } ], "extra": [ 1, 99, 169, 161, 67, 201, 107, 139, 7, 208, 108, 181, 229, 240, 222, 201, 206, 206, 158, 193, 53, 229, 19, 34, 208, 70, 53, 98, 55, 55, 130, 130, 141, 2, 17, 0, 0, 0, 1, 241, 136, 200, 168, 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: