Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f038aa27ae4529b3b149ea9a6ac196804c35a0e2b9f5b4aab65e711d4e1d90e

Tx prefix hash: 6623c9848224a12e6ab4fdf575d4074de1878a43816a62febe98ef872756d650
Tx public key: afee9a0d7f634b29b0ea8c1d88081ca6d50b4b8750c27224ed29af8dd549a2a5
Timestamp: 1742329671 Timestamp [UTC]: 2025-03-18 20:27:51 Age [y:d:h:m:s]: 01:247:23:50:16
Block: 1242220 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 441274 RingCT/type: yes/0
Extra: 01afee9a0d7f634b29b0ea8c1d88081ca6d50b4b8750c27224ed29af8dd549a2a50211000000081f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 352a7ea685d32ac07ef234fa1171f98f6035b27d5176d2102961d4bedf4d12d2 0.000600000000 1729193 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": 1242230, "vin": [ { "gen": { "height": 1242220 } } ], "vout": [ { "amount": 600000000, "target": { "key": "352a7ea685d32ac07ef234fa1171f98f6035b27d5176d2102961d4bedf4d12d2" } } ], "extra": [ 1, 175, 238, 154, 13, 127, 99, 75, 41, 176, 234, 140, 29, 136, 8, 28, 166, 213, 11, 75, 135, 80, 194, 114, 36, 237, 41, 175, 141, 213, 73, 162, 165, 2, 17, 0, 0, 0, 8, 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: