← previous blocknext block →recent activity
Analyzing
Block #91,252,956
20 transactions · 19 stateful · 2026-07-29 04:50:32 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,252,956 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w27w28w310w311w412w513w516w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8ce30a38…ec7e
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xbbeac3b7…c14b
0x34b655…2a6f
6 touches
3 conflicts
0xfbe6a366…8ca1
0x34b655…2a6f
6 touches
3 conflicts
0x2ada3e8e…960f
0x34b655…2a6f
4 touches
1 conflict
0x365ca418…bea4
0x34b655…2a6f
4 touches
1 conflict
0x38e39eef…50bd
0x34b655…2a6f
4 touches
1 conflict
0x3b9bb58c…e73a
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 0x8ce30a38ab…1bec7e
Audit this contract →
← previous block·next block →recent activity