← previous blocknext block →recent activity
Analyzing
Block #91,131,406
29 transactions · 28 stateful · 2026-07-28 18:39:01 UTC
Parallelism
93/100
Blocked
7%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,131,406 · 29 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
21w023w126w027w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3796ff96…4de6
0x34b655…2a6f
4 touches
1 conflict
0x4cb89fd4…9bb8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64dc
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x219c6953…c961
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 0x3796ff96a7…6f4de6
Audit this contract →
← previous block·next block →recent activity