← previous blocknext block →recent activity
Analyzing
Block #91,111,943
8 transactions · 8 stateful · 2026-07-28 17:01:07 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,111,943 · 8 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
2w03w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xb39cb1d8…effa
0x34b655…2a6f
4 touches
1 conflict
0x06c2c8c1…c2a8
0x34b655…2a6f
2 touches
0 conflicts
0x06c2c8c1…c2a9
0x34b655…2a6f
2 touches
0 conflicts
0x07481446…d90f
0x34b655…2a6f
2 touches
0 conflicts
0x0957b324…1dc6
0x34b655…2a6f
2 touches
0 conflicts
0x0fd1ecf0…ee41
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity