← previous blocknext block →recent activity
Analyzing
Block #99,866,353
21 transactions · 16 stateful · 2026-08-28 09:47:00 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,866,353 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w19w011w112w213w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x231b3fa5…5466
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
0xec2a8d79…70cb
0x34b655…2a6f
4 touches
1 conflict
0x10a5a231…be40
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x3243e72f…1f6d
0x34b655…2a6f
4 touches
1 conflict
0x38bcfe5f…6c71
0x34b655…2a6f
4 touches
1 conflict
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: Perpl
6 conflicts on slot 0x231b3fa50b…eb5466
Audit this contract →
← previous block·next block →recent activity