← previous blocknext block →recent activity
Analyzing
Block #91,009,632
11 transactions · 11 stateful · 2026-07-28 08:26:12 UTC
Parallelism
82/100
Blocked
27%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,009,632 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w16w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7fb66e8…4f94
0x34b655…2a6f
4 touches
1 conflict
0xcabb7f1d…ebbe
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x9a9eea06…1cfa
0x34b655…2a6f
4 touches
1 conflict
0x1ed6aee3…3f17
0x34b655…2a6f
4 touches
1 conflict
0x4bfdcd51…9b58
0x34b655…2a6f
2 touches
0 conflicts
0x6ca0994e…02ef
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 0xb7fb66e892…ec4f94
Audit this contract →
← previous block·next block →recent activity