← previous blocknext block →recent activity
Analyzing
Block #98,755,308
20 transactions · 19 stateful · 2026-08-24 12:15:20 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,755,308 · 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
1w04w05w18w09w110w111w212w314w115w416w518w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x9c83a7b1…e305
0x34b655…2a6f
8 touches
6 conflicts
0x05283eab…97f8
0x34b655…2a6f
6 touches
3 conflicts
0x152f8e3d…3da0
0x34b655…2a6f
6 touches
3 conflicts
0x9d807d24…6235
0x34b655…2a6f
6 touches
3 conflicts
0x9dccd2a9…2790
0x34b655…2a6f
6 touches
3 conflicts
0xdced0536…ba3d
0x34b655…2a6f
6 touches
3 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: Perpl
10 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity