Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5d3f18fbb5bb883327dba1bead91b0346cc4746e7f4d0671239cda19abeed48

Tx prefix hash: 4751e35038075de04fd6925fbe00521f8cac94467d2d3fbcbd861c4f46f77109
Tx public key: cd8828244bb364a8dfa8e6eb26bba2d7cb2498843ed1a2747873069e90ec4696
Timestamp: 1747196289 Timestamp [UTC]: 2025-05-14 04:18:09 Age [y:d:h:m:s]: 01:003:01:26:51
Block: 1282494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253161 RingCT/type: yes/0
Extra: 01cd8828244bb364a8dfa8e6eb26bba2d7cb2498843ed1a2747873069e90ec46960211000000081f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3df051865e1be3284d47b74204fcde0ca96bbfedf0dca3e3f7baa8bb31b40a8a 0.000600000000 1769901 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": 1282504, "vin": [ { "gen": { "height": 1282494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3df051865e1be3284d47b74204fcde0ca96bbfedf0dca3e3f7baa8bb31b40a8a" } } ], "extra": [ 1, 205, 136, 40, 36, 75, 179, 100, 168, 223, 168, 230, 235, 38, 187, 162, 215, 203, 36, 152, 132, 62, 209, 162, 116, 120, 115, 6, 158, 144, 236, 70, 150, 2, 17, 0, 0, 0, 8, 31, 144, 81, 122, 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: