Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec21533fe2d7ba1ab76b2d18ad4024da47b061dbf002e37d4aaf5fc4876fe730

Tx prefix hash: a3495e84e9c598ed58c56beeb7949a0cab5ca7c4ccb0e6831ae2ccdbf26a122d
Tx public key: 44373a377dc62e7c36f4c39183ad0f5f470b8dae8f25f6adf2548cf74c5f76fd
Timestamp: 1771578211 Timestamp [UTC]: 2026-02-20 09:03:31 Age [y:d:h:m:s]: 00:271:05:19:52
Block: 1481821 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199364 RingCT/type: yes/0
Extra: 0144373a377dc62e7c36f4c39183ad0f5f470b8dae8f25f6adf2548cf74c5f76fd021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2c0664eccb635ae8a7bfd67bf8bebf1fb45ee3f41c1620d04160c9794b337253 0.000600000000 1971207 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": 1481831, "vin": [ { "gen": { "height": 1481821 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c0664eccb635ae8a7bfd67bf8bebf1fb45ee3f41c1620d04160c9794b337253" } } ], "extra": [ 1, 68, 55, 58, 55, 125, 198, 46, 124, 54, 244, 195, 145, 131, 173, 15, 95, 71, 11, 141, 174, 143, 37, 246, 173, 242, 84, 140, 247, 76, 95, 118, 253, 2, 17, 0, 0, 0, 4, 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: