Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc2a576cb600bfc98c165a3d553261392bfeebccb57126ca9d5570afc560cb84

Tx prefix hash: 2111311ac3a627b545b033d847b3b046cc1680aaa9aae2b97098142eca4ed143
Tx public key: c95d0c5895aeade1c9ff43770ab48d42a8b34e745ccb0978b8e19af2a15baa71
Timestamp: 1742118298 Timestamp [UTC]: 2025-03-16 09:44:58 Age [y:d:h:m:s]: 01:251:12:20:56
Block: 1240471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443679 RingCT/type: yes/0
Extra: 01c95d0c5895aeade1c9ff43770ab48d42a8b34e745ccb0978b8e19af2a15baa710211000000021f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 004c6f9875964d4b090c99b67a3af72880468715b7dfeb9456281e95eac760de 0.000600000000 1727444 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": 1240481, "vin": [ { "gen": { "height": 1240471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "004c6f9875964d4b090c99b67a3af72880468715b7dfeb9456281e95eac760de" } } ], "extra": [ 1, 201, 93, 12, 88, 149, 174, 173, 225, 201, 255, 67, 119, 10, 180, 141, 66, 168, 179, 78, 116, 92, 203, 9, 120, 184, 225, 154, 242, 161, 91, 170, 113, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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: