Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 386c78cd15bf9b45a1e00a942f87354946bf16bac78549c9e2d3d7a5f0157d2a

Tx prefix hash: 365453fb834cedfd78f0a1836829b64d1d34b914bdf07d7b42b610f764346836
Tx public key: 5bbade3edf95b5e6ef8334765d13e2bf03b09f0ef8b887206faa19eeefc219db
Timestamp: 1744323335 Timestamp [UTC]: 2025-04-10 22:15:35 Age [y:d:h:m:s]: 01:218:01:02:51
Block: 1258705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419767 RingCT/type: yes/0
Extra: 015bbade3edf95b5e6ef8334765d13e2bf03b09f0ef8b887206faa19eeefc219db021100000003dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b20f30e5363d47727796e1a55224184a873c1d53b53011701b2721dcada923dc 0.000600000000 1745842 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": 1258715, "vin": [ { "gen": { "height": 1258705 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b20f30e5363d47727796e1a55224184a873c1d53b53011701b2721dcada923dc" } } ], "extra": [ 1, 91, 186, 222, 62, 223, 149, 181, 230, 239, 131, 52, 118, 93, 19, 226, 191, 3, 176, 159, 14, 248, 184, 135, 32, 111, 170, 25, 238, 239, 194, 25, 219, 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: