Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69cf62cb75b1f8db7661afcf1a2d937cf4eca5ffbb6b618231b3764298b4007e

Tx prefix hash: db4c967655d1b7d0f1515a60ed7eda8ce23f7809d8cae8c1a32098a831877436
Tx public key: 42b8d9acc87df9af68620de5cddcf59103e850ecb8a1ea4eecce0fa94f198ec3
Timestamp: 1760936113 Timestamp [UTC]: 2025-10-20 04:55:13 Age [y:d:h:m:s]: 01:026:09:54:11
Block: 1393835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285128 RingCT/type: yes/0
Extra: 0142b8d9acc87df9af68620de5cddcf59103e850ecb8a1ea4eecce0fa94f198ec302110000000225a35a0f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1ae3e990616bace14d26186e8ef8b69ef044bbf03353f37d79df53211c44ccc4 0.000600000000 1882102 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": 1393845, "vin": [ { "gen": { "height": 1393835 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ae3e990616bace14d26186e8ef8b69ef044bbf03353f37d79df53211c44ccc4" } } ], "extra": [ 1, 66, 184, 217, 172, 200, 125, 249, 175, 104, 98, 13, 229, 205, 220, 245, 145, 3, 232, 80, 236, 184, 161, 234, 78, 236, 206, 15, 169, 79, 25, 142, 195, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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: