← previous blocknext block →recent activity
Analyzing
Block #91,808,175
23 transactions · 21 stateful · 2026-07-31 03:25:53 UTC
Parallelism
78/100
Blocked
33%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,808,175 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w18w213w116w317w421w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d651956…12e8
0x34b655…2a6f
8 touches
6 conflicts
0x5d9e6c20…078c
0x34b655…2a6f
6 touches
3 conflicts
0xb9834665…e363
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x6083af24…a0df
0x34b655…2a6f
6 touches
3 conflicts
0x4e9832a1…7b8c
0x34b655…2a6f
4 touches
1 conflict
0x4f2fabb0…9b09
0x34b655…2a6f
4 touches
1 conflict
0x522e20b4…fbc4
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 0x2d65195682…4112e8
Audit this contract →
← previous block·next block →recent activity