← previous blocknext block →recent activity
Analyzing
Block #83,412,742
16 transactions · 15 stateful · 2026-06-24 15:36:24 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,412,742 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w25w36w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b16149e…7d4d
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x61e33703…a594
0x065c9d…c394
2 touches
0 conflicts
0x8d9be5ec…c09f
0x065c9d…c394
2 touches
0 conflicts
0xa590396f…cb79
0x065c9d…c394
2 touches
0 conflicts
0xac0ab07a…07d6
0x065c9d…c394
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Kuru Exchange: Market-MON/USDC
6 conflicts on slot 0x0b16149e0d…887d4d
Audit this contract →
← previous block·next block →recent activity