Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 342a820a045cc6e4dbc29eedd19a1d7bfa4aaaa3b829101ef99d3bac0f38636c

Tx prefix hash: 1917508dd47ea732f5f912e2a1174ac374df520e184d285feb0b25179ef8b58d
Tx public key: 88e53dfbaeba8b6dde88627ea558c866c27e5b24d14728a2cb3d8ae0a18e747d
Timestamp: 1771264450 Timestamp [UTC]: 2026-02-16 17:54:10 Age [y:d:h:m:s]: 00:093:03:51:57
Block: 1479204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60062 RingCT/type: yes/0
Extra: 0188e53dfbaeba8b6dde88627ea558c866c27e5b24d14728a2cb3d8ae0a18e747d021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 61c76c42532716464243ea1a4350f505db49ae4f7c5fca30dd51685148f0fde1 0.000600000000 1968544 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": 1479214, "vin": [ { "gen": { "height": 1479204 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61c76c42532716464243ea1a4350f505db49ae4f7c5fca30dd51685148f0fde1" } } ], "extra": [ 1, 136, 229, 61, 251, 174, 186, 139, 109, 222, 136, 98, 126, 165, 88, 200, 102, 194, 126, 91, 36, 209, 71, 40, 162, 203, 61, 138, 224, 161, 142, 116, 125, 2, 17, 0, 0, 0, 1, 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: