Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc9df53201bdd351442405cebaffb2dfde0efeb3c86b130b8ea7613ffd54d1e5

Tx prefix hash: 0f87162c3621aabb363edff04b0e4a4d3b79622539db779f2c746de1f89ff5e2
Tx public key: dee023f0d8d404fc50a9d319e1a8680bf4e53529e578c0ed30ee203c728a7d80
Timestamp: 1785097385 Timestamp [UTC]: 2026-07-26 20:23:05 Age [y:d:h:m:s]: 00:114:01:04:23
Block: 1596856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 83801 RingCT/type: yes/0
Extra: 01dee023f0d8d404fc50a9d319e1a8680bf4e53529e578c0ed30ee203c728a7d80

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a50af8b5fd47364c0f7905dea71680c9d53254505f7f2f812a5bc59b3ba5b56e 0.000600000000 2086874 of 15 <74>

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": 1596866, "vin": [ { "gen": { "height": 1596856 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "a50af8b5fd47364c0f7905dea71680c9d53254505f7f2f812a5bc59b3ba5b56e", "view_tag": "74" } } } ], "extra": [ 1, 222, 224, 35, 240, 216, 212, 4, 252, 80, 169, 211, 25, 225, 168, 104, 11, 244, 229, 53, 41, 229, 120, 192, 237, 48, 238, 32, 60, 114, 138, 125, 128 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: