Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66df3833a28582461505c918fcf4f09f4980a22016e5f1e5294f247e014e5436

Tx prefix hash: fc48eaf1af33067b0aa600e991ec8f1f5cc37483955985d26487e4824e1c444f
Tx public key: 005cdd2eb9fd74209f99a751c26ae5a034961db47a7b4a64a368f47ffd7411f3
Timestamp: 1772155370 Timestamp [UTC]: 2026-02-27 01:22:50 Age [y:d:h:m:s]: 00:268:08:20:29
Block: 1486577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196917 RingCT/type: yes/0
Extra: 01005cdd2eb9fd74209f99a751c26ae5a034961db47a7b4a64a368f47ffd7411f3021100000005f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 29f185628e9d667d3e8221a879be3d7a41e2bcff90a8a38eefbc3826a87fe317 0.000600000000 1976033 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": 1486587, "vin": [ { "gen": { "height": 1486577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29f185628e9d667d3e8221a879be3d7a41e2bcff90a8a38eefbc3826a87fe317" } } ], "extra": [ 1, 0, 92, 221, 46, 185, 253, 116, 32, 159, 153, 167, 81, 194, 106, 229, 160, 52, 150, 29, 180, 122, 123, 74, 100, 163, 104, 244, 127, 253, 116, 17, 243, 2, 17, 0, 0, 0, 5, 241, 136, 200, 168, 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: