← previous blocknext block →recent activity
Analyzing
Block #91,957,373
10 transactions · 9 stateful · 2026-07-31 15:56:32 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,957,373 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4bf59d22…00de
0x34b655…2a6f
4 touches
1 conflict
0x4e135144…4167
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x2399f0e0…f943
0x34b655…2a6f
2 touches
0 conflicts
0x27034002…2f27
0x34b655…2a6f
2 touches
0 conflicts
0x27f0e3c6…f709
0x34b655…2a6f
2 touches
0 conflicts
0x3717630d…481b
0x34b655…2a6f
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: Perpl
1 conflict on slot 0x4bf59d22eb…3300de
Audit this contract →
← previous block·next block →recent activity