Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f98d94dddccd48bf45e64ae89c0aa1e6d57577a9ff3bb5844386bcd532db23cc

Tx prefix hash: dd0678475a3bcc44b6b5f8e14d70718d937185730cfdad308aa0c7b6eaa482a1
Tx public key: 7d65192947978c01c280f416e41266d48bc1073ac265c40b74cce450e8a1fb17
Timestamp: 1744278607 Timestamp [UTC]: 2025-04-10 09:50:07 Age [y:d:h:m:s]: 01:215:09:57:54
Block: 1258337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417744 RingCT/type: yes/0
Extra: 017d65192947978c01c280f416e41266d48bc1073ac265c40b74cce450e8a1fb17021100000003dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e2c4ffcdd5e33c18a08b56f4703e52e2099973fed31a121483bd5ef8048d0a8d 0.000600000000 1745470 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": 1258347, "vin": [ { "gen": { "height": 1258337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2c4ffcdd5e33c18a08b56f4703e52e2099973fed31a121483bd5ef8048d0a8d" } } ], "extra": [ 1, 125, 101, 25, 41, 71, 151, 140, 1, 194, 128, 244, 22, 228, 18, 102, 212, 139, 193, 7, 58, 194, 101, 196, 11, 116, 204, 228, 80, 232, 161, 251, 23, 2, 17, 0, 0, 0, 3, 219, 181, 113, 193, 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: