Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 042db9e2aa2a2cd90cf3e166a50cfbcb5b1be3ee04d187141669c1a499182487

Tx prefix hash: 761c9b06161e67b7c2f4306d60734596ff3a834652c4b82ac2146e3e6859c00e
Tx public key: ee072bf3eefb6d55a4ddabc85e760e6689a729a253d4dda3758ba09f0ddb9794
Timestamp: 1758174978 Timestamp [UTC]: 2025-09-18 05:56:18 Age [y:d:h:m:s]: 01:049:22:36:17
Block: 1370933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301411 RingCT/type: yes/0
Extra: 01ee072bf3eefb6d55a4ddabc85e760e6689a729a253d4dda3758ba09f0ddb9794021100000008b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: df84547b61296ceebc29c0ba696d581d54c0767d4d33d308ff6011ec73392282 0.000600000000 1859010 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": 1370943, "vin": [ { "gen": { "height": 1370933 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df84547b61296ceebc29c0ba696d581d54c0767d4d33d308ff6011ec73392282" } } ], "extra": [ 1, 238, 7, 43, 243, 238, 251, 109, 85, 164, 221, 171, 200, 94, 118, 14, 102, 137, 167, 41, 162, 83, 212, 221, 163, 117, 139, 160, 159, 13, 219, 151, 148, 2, 17, 0, 0, 0, 8, 178, 247, 132, 196, 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: