Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dc12ec1fa81c0d291ebcc6d10cc68a31a560015402d79505e7e23dcb02be41d

Tx prefix hash: 444b4b03cf0dbb4a68fb29f8c7b9ca3cbaf546f435f9ad37ed587c4f7b462d80
Tx public key: 1802369b5d50cc6b783a2d1995b953aedeb51b9b084f7192083319a1c9b7ec72
Timestamp: 1773212959 Timestamp [UTC]: 2026-03-11 07:09:19 Age [y:d:h:m:s]: 00:254:00:54:08
Block: 1495331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187195 RingCT/type: yes/0
Extra: 011802369b5d50cc6b783a2d1995b953aedeb51b9b084f7192083319a1c9b7ec72021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d5be85b6b57688346f7da85df8426d16790568a8400e6da4bb4df8c33b16742c 0.000600000000 1984941 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": 1495341, "vin": [ { "gen": { "height": 1495331 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5be85b6b57688346f7da85df8426d16790568a8400e6da4bb4df8c33b16742c" } } ], "extra": [ 1, 24, 2, 54, 155, 93, 80, 204, 107, 120, 58, 45, 25, 149, 185, 83, 174, 222, 181, 27, 155, 8, 79, 113, 146, 8, 51, 25, 161, 201, 183, 236, 114, 2, 17, 0, 0, 0, 3, 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: