Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 314d080d2bcb561b95f3c8b4851c0305aec444e2818f0e4b34dca694a7db6620

Tx prefix hash: 85b7ae7b9eddf7aef5859e763d9483702917d5ce706284457063c352a4fe187c
Tx public key: c779d596b6df84379422bc7f7893bd125ea2715e5f17b95838e3be34b85ee8bf
Timestamp: 1775130631 Timestamp [UTC]: 2026-04-02 11:50:31 Age [y:d:h:m:s]: 00:231:01:44:07
Block: 1511197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170726 RingCT/type: yes/0
Extra: 01c779d596b6df84379422bc7f7893bd125ea2715e5f17b95838e3be34b85ee8bf021100000001e3d7dc9f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d53bf607e32f123af2f63c0b2252e6c29e91534fb0b71dea6ffc0eea5c522aea 0.000600000000 2000987 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": 1511207, "vin": [ { "gen": { "height": 1511197 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d53bf607e32f123af2f63c0b2252e6c29e91534fb0b71dea6ffc0eea5c522aea" } } ], "extra": [ 1, 199, 121, 213, 150, 182, 223, 132, 55, 148, 34, 188, 127, 120, 147, 189, 18, 94, 162, 113, 94, 95, 23, 185, 88, 56, 227, 190, 52, 184, 94, 232, 191, 2, 17, 0, 0, 0, 1, 227, 215, 220, 159, 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: