Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3934b95b40adadf50d9399d4cb9f80d2b0b07a9595467c35cb395cf5a17583ca

Tx prefix hash: 0179cb5665f559f3e2ddc66928398fa8c5dc84509e4260a14c3a7802692e95ea
Tx public key: 83201ccdac4fe773e7774478285037365160a4fd97a8b12250e0ed8481628cf3
Timestamp: 1773188382 Timestamp [UTC]: 2026-03-11 00:19:42 Age [y:d:h:m:s]: 00:255:14:23:49
Block: 1495131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188345 RingCT/type: yes/0
Extra: 0183201ccdac4fe773e7774478285037365160a4fd97a8b12250e0ed8481628cf3021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c8ef89803c620d08b9a9cdff24e2e2a5f798b5b752db28d520d144fc7f76ee9d 0.000600000000 1984739 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": 1495141, "vin": [ { "gen": { "height": 1495131 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8ef89803c620d08b9a9cdff24e2e2a5f798b5b752db28d520d144fc7f76ee9d" } } ], "extra": [ 1, 131, 32, 28, 205, 172, 79, 231, 115, 231, 119, 68, 120, 40, 80, 55, 54, 81, 96, 164, 253, 151, 168, 177, 34, 80, 224, 237, 132, 129, 98, 140, 243, 2, 17, 0, 0, 0, 3, 228, 245, 25, 63, 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: