Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edddb2bf0a2dcb4c31c176da0fbec3f9611dc127905d76f0ac583e3ce5facb7f

Tx prefix hash: 9a96721f1a5659d9e5553fefb43e781bc687cd46357c965a7e7dd5e69e2424aa
Tx public key: fc857dbf80cb9583e11b2712eefbbf3a3d284f7278e766a8a5bb94b13e48ad17
Timestamp: 1773310607 Timestamp [UTC]: 2026-03-12 10:16:47 Age [y:d:h:m:s]: 00:249:19:18:35
Block: 1496152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184018 RingCT/type: yes/0
Extra: 01fc857dbf80cb9583e11b2712eefbbf3a3d284f7278e766a8a5bb94b13e48ad17021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b16f7342809f811da52cb1ffb98d9eb108847762b30413a6c21e522e2a8eaf7a 0.000600000000 1985774 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": 1496162, "vin": [ { "gen": { "height": 1496152 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b16f7342809f811da52cb1ffb98d9eb108847762b30413a6c21e522e2a8eaf7a" } } ], "extra": [ 1, 252, 133, 125, 191, 128, 203, 149, 131, 225, 27, 39, 18, 238, 251, 191, 58, 61, 40, 79, 114, 120, 231, 102, 168, 165, 187, 148, 177, 62, 72, 173, 23, 2, 17, 0, 0, 0, 2, 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: