Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b850f98eb04ffec454dec6aa9c838c1a990e3dab3dea8340060a649deb9c1ba

Tx prefix hash: 253301296e3cccb67f4ae50a2b5864d128a09e1add29eb75b0c0ec3b9563ca9c
Tx public key: 8b3390c224d6a4e628a64323a3e2f44d175fe3dea70fce0304fe198c9bdbddf1
Timestamp: 1771782944 Timestamp [UTC]: 2026-02-22 17:55:44 Age [y:d:h:m:s]: 00:269:18:57:41
Block: 1483511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198383 RingCT/type: yes/0
Extra: 018b3390c224d6a4e628a64323a3e2f44d175fe3dea70fce0304fe198c9bdbddf1021100000005f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 92baeda3317682b2cc4a6e316ea55d249c3387f147be0fb12f6ed10bc84e3407 0.000600000000 1972921 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": 1483521, "vin": [ { "gen": { "height": 1483511 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92baeda3317682b2cc4a6e316ea55d249c3387f147be0fb12f6ed10bc84e3407" } } ], "extra": [ 1, 139, 51, 144, 194, 36, 214, 164, 230, 40, 166, 67, 35, 163, 226, 244, 77, 23, 95, 227, 222, 167, 15, 206, 3, 4, 254, 25, 140, 155, 219, 221, 241, 2, 17, 0, 0, 0, 5, 241, 136, 200, 168, 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: