← previous blocknext block →recent activity
Analyzing
Block #91,770,414
9 transactions · 9 stateful · 2026-07-31 00:15:56 UTC
Parallelism
78/100
Blocked
22%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,770,414 · 9 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
1w02w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31b39922…1e65
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0327b211…2766
0x34b655…2a6f
2 touches
0 conflicts
0x092b4267…08a8
0x34b655…2a6f
2 touches
0 conflicts
0x20bfdd90…60df
0x34b655…2a6f
2 touches
0 conflicts
0x25bdc7e4…b92e
0x34b655…2a6f
2 touches
0 conflicts
0x3f5f366d…10d9
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 0x31b3992285…921e65
Audit this contract →
← previous block·next block →recent activity