← previous blocknext block →recent activity
Analyzing
Block #91,275,968
22 transactions · 20 stateful · 2026-07-29 06:47:03 UTC
Parallelism
68/100
Blocked
45%
Avg conflicts / tx
0.82
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,275,968 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w06w07w18w29w012w313w415w116w118w519w620w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc0eb79d1…29a4
0x34b655…2a6f
6 touches
3 conflicts
0x65f90aa4…c97f
0x34b655…2a6f
6 touches
3 conflicts
0x8765edd1…a7d5
0x34b655…2a6f
4 touches
1 conflict
0x9b86aa76…6f62
0x34b655…2a6f
4 touches
1 conflict
0xb9834665…e363
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity