← previous blocknext block →recent activity
Analyzing
Block #91,769,991
14 transactions · 12 stateful · 2026-07-31 00:13:48 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,769,991 · 14 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
2w03w14w27w09w110w112w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x673e2e56…9f5d
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x0c77d84b…971e
0x34b655…2a6f
4 touches
1 conflict
0x0f00f2df…7579
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x26040a51…4b8c
0x34b655…2a6f
4 touches
1 conflict
0x329f2f7d…dcff
0x34b655…2a6f
4 touches
1 conflict
0x36c32ad6…25d0
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
3 conflicts on slot 0x673e2e5652…b99f5d
Audit this contract →
← previous block·next block →recent activity