← previous blocknext block →recent activity
Analyzing
Block #91,110,844
20 transactions · 20 stateful · 2026-07-28 16:55:35 UTC
Parallelism
60/100
Blocked
55%
Avg conflicts / tx
1.1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,110,844 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w16w27w38w49w510w111w612w114w317w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x2d651956…12e8
0x34b655…2a6f
8 touches
6 conflicts
0x5c16527f…628c
0x34b655…2a6f
6 touches
3 conflicts
0x0beb7088…592e
0x34b655…2a6f
6 touches
3 conflicts
0x36a76bd2…1fb0
0x34b655…2a6f
4 touches
1 conflict
0x3a996b35…bc8f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x805d08cf…3cfc
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity