Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f96d1e0bffe635fcf66b348404921c4b4e529bb9881d68de4af77c1163b57868

Tx prefix hash: 8e8db2e344b38f57fb2976a760bc947da32bc6d8e58e05192acc83a08d9fff97
Tx public key: 8abf6f23ca91ea5249013b268ec1f3ad7dcf727f012ea4d40fd0ab219929406f
Timestamp: 1769698750 Timestamp [UTC]: 2026-01-29 14:59:10 Age [y:d:h:m:s]: 00:111:01:57:00
Block: 1466254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72872 RingCT/type: yes/0
Extra: 018abf6f23ca91ea5249013b268ec1f3ad7dcf727f012ea4d40fd0ab219929406f021100000005215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6626eb6b57f262154ca26ce559da3c19e1c5c505e26f7c82562d2b998287a00d 0.000600000000 1955488 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": 1466264, "vin": [ { "gen": { "height": 1466254 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6626eb6b57f262154ca26ce559da3c19e1c5c505e26f7c82562d2b998287a00d" } } ], "extra": [ 1, 138, 191, 111, 35, 202, 145, 234, 82, 73, 1, 59, 38, 142, 193, 243, 173, 125, 207, 114, 127, 1, 46, 164, 212, 15, 208, 171, 33, 153, 41, 64, 111, 2, 17, 0, 0, 0, 5, 33, 91, 191, 137, 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: