Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e694b192ae1e95858e7f6922ca9761997ffdd5144824f36b5a8aa7cd58ca4df8

Tx prefix hash: e9b482a4b6137e72954feb804f3d252454e7cfad4c85abb798408af56b2e03b8
Tx public key: 0ca8bb58a25a7933fbdfa72ff3b62cb0b2d58b50d18d4eec1ef431359eb915b7
Timestamp: 1760637702 Timestamp [UTC]: 2025-10-16 18:01:42 Age [y:d:h:m:s]: 01:034:08:42:40
Block: 1391351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290992 RingCT/type: yes/0
Extra: 010ca8bb58a25a7933fbdfa72ff3b62cb0b2d58b50d18d4eec1ef431359eb915b70211000000022609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0dd2c7d207190aa52940a5a5fd81a500b3cc22960127f38cb5e2053eba56181b 0.000600000000 1879598 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": 1391361, "vin": [ { "gen": { "height": 1391351 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0dd2c7d207190aa52940a5a5fd81a500b3cc22960127f38cb5e2053eba56181b" } } ], "extra": [ 1, 12, 168, 187, 88, 162, 90, 121, 51, 251, 223, 167, 47, 243, 182, 44, 176, 178, 213, 139, 80, 209, 141, 78, 236, 30, 244, 49, 53, 158, 185, 21, 183, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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: