← previous blocknext block →recent activity
Analyzing
Block #91,126,159
11 transactions · 10 stateful · 2026-07-28 18:12:38 UTC
Parallelism
73/100
Blocked
30%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,126,159 · 11 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
1w02w03w17w08w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xbc66586e…20fe
0x34b655…2a6f
4 touches
1 conflict
0x05414787…6b5b
0x34b655…2a6f
2 touches
0 conflicts
0x0f4fd7ed…38fa
0x34b655…2a6f
2 touches
0 conflicts
0x2c00f6a5…a865
0x34b655…2a6f
2 touches
0 conflicts
0x3601aa45…29cb
0x34b655…2a6f
2 touches
0 conflicts
0x536c239d…d9c9
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity