← previous blocknext block →recent activity
Analyzing
Block #91,009,238
12 transactions · 11 stateful · 2026-07-28 08:24:12 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,009,238 · 12 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
2w06w07w19w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c7f2108…99fc
0x34b655…2a6f
4 touches
1 conflict
0x2c7f2108…99fd
0x34b655…2a6f
4 touches
1 conflict
0x2cc85280…c2f7
0x34b655…2a6f
4 touches
1 conflict
0x7133f06a…742a
0x34b655…2a6f
4 touches
1 conflict
0x8ce1ffed…4889
0x34b655…2a6f
4 touches
1 conflict
0x95dd1dda…bc0e
0x34b655…2a6f
4 touches
1 conflict
0xb0e11936…07cc
0x34b655…2a6f
4 touches
1 conflict
0xc014bcf3…3ac7
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
1 conflict on slot 0x2c7f21086d…6899fc
Audit this contract →
← previous block·next block →recent activity