← previous blocknext block →recent activity
Analyzing
Block #98,779,426
20 transactions · 19 stateful · 2026-08-24 14:16:43 UTC
Parallelism
70/100
Blocked
37%
Avg conflicts / tx
0.75
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,779,426 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w27w38w010w112w313w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x9c168b41…7486
0x34b655…2a6f
6 touches
3 conflicts
0xb1a21f19…3e56
0x34b655…2a6f
6 touches
3 conflicts
0x0d03bddb…6658
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xfefb0189…f726
0x34b655…2a6f
4 touches
1 conflict
0xb9b077a8…e029
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity