Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33680adbe554ed630a814ffa1e86babff337b3dd4a2c4364df2c78b49481e378

Tx prefix hash: 2279bbcda976e88862fa6b457933b0beeffbb33b61ee2aa0c9a36bc0b522d6fc
Tx public key: 3163ed5053338581b6be9267cbe8fd47a7dd014763e4cdaec36f3b0ca77d272b
Timestamp: 1743506926 Timestamp [UTC]: 2025-04-01 11:28:46 Age [y:d:h:m:s]: 01:038:09:36:31
Block: 1251939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278676 RingCT/type: yes/0
Extra: 013163ed5053338581b6be9267cbe8fd47a7dd014763e4cdaec36f3b0ca77d272b0211000000064060f6d2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dc507461827d59eb9aada00d756cc6398a582a0d5c4e2289d23aaabff1c629fc 0.000600000000 1739016 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": 1251949, "vin": [ { "gen": { "height": 1251939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc507461827d59eb9aada00d756cc6398a582a0d5c4e2289d23aaabff1c629fc" } } ], "extra": [ 1, 49, 99, 237, 80, 83, 51, 133, 129, 182, 190, 146, 103, 203, 232, 253, 71, 167, 221, 1, 71, 99, 228, 205, 174, 195, 111, 59, 12, 167, 125, 39, 43, 2, 17, 0, 0, 0, 6, 64, 96, 246, 210, 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: