← previous blocknext block →recent activity
Analyzing
Block #91,969,196
11 transactions · 9 stateful · 2026-07-31 16:55:59 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,969,196 · 11 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
1w03w05w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56153262…21ce
0x34b655…2a6f
4 touches
1 conflict
0x5e2aa1dd…83c9
0x34b655…2a6f
4 touches
1 conflict
0x0ba865dd…a249
0x34b655…2a6f
2 touches
0 conflicts
0x0df19edb…2682
0x34b655…2a6f
2 touches
0 conflicts
0x184b6e8c…513a
0x34b655…2a6f
2 touches
0 conflicts
0x1a71b30e…bde1
0x34b655…2a6f
2 touches
0 conflicts
0x1c0542a8…811e
0x34b655…2a6f
2 touches
0 conflicts
0x1dd79365…4bab
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 0x5615326245…a221ce
Audit this contract →
← previous block·next block →recent activity