Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02a2b8430786fe2f364d1da7fafea7fc1e9c28cb3efaed8ce766161e6329feeb

Tx prefix hash: 3fc7609d108d494ed49a892a0617935637291293a009bd2fc1ec7ad906796687
Tx public key: dd7c217bdf2e225da492b32eff4d527d6e77e11fec7ae79b232a679117ff80c1
Timestamp: 1775017704 Timestamp [UTC]: 2026-04-01 04:28:24 Age [y:d:h:m:s]: 00:232:11:47:43
Block: 1510269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171734 RingCT/type: yes/0
Extra: 01dd7c217bdf2e225da492b32eff4d527d6e77e11fec7ae79b232a679117ff80c1021100000004e3d7dc9f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 86fae5f06a8e3267a8b611270f1112f386c6b83a02f1eab238cf50cb66913ad9 0.000600000000 2000051 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": 1510279, "vin": [ { "gen": { "height": 1510269 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86fae5f06a8e3267a8b611270f1112f386c6b83a02f1eab238cf50cb66913ad9" } } ], "extra": [ 1, 221, 124, 33, 123, 223, 46, 34, 93, 164, 146, 179, 46, 255, 77, 82, 125, 110, 119, 225, 31, 236, 122, 231, 155, 35, 42, 103, 145, 23, 255, 128, 193, 2, 17, 0, 0, 0, 4, 227, 215, 220, 159, 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: