← previous blocknext block →recent activity
Analyzing
Block #91,109,518
9 transactions · 8 stateful · 2026-07-28 16:48:55 UTC
Parallelism
56/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,109,518 · 9 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xb9834665…e363
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x03c76d4b…8294
0x34b655…2a6f
2 touches
0 conflicts
0x124a2fe8…2ea9
0x34b655…2a6f
2 touches
0 conflicts
0x17b79a67…73c2
0x34b655…2a6f
2 touches
0 conflicts
0x1de49243…4aa3
0x34b655…2a6f
2 touches
0 conflicts
0x20f13ae0…cca8
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