← previous blocknext block →recent activity
Analyzing
Block #91,070,921
20 transactions · 17 stateful · 2026-07-28 13:34:39 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,070,921 · 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
1w02w03w14w28w19w210w311w412w516w418w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x6f900be0…cd6e
0x34b655…2a6f
6 touches
3 conflicts
0x0ab54c30…b88e
0x34b655…2a6f
6 touches
3 conflicts
0x427d1120…4eb1
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x6d9bea1c…2ca1
0x34b655…2a6f
6 touches
3 conflicts
0xf219f7cf…7379
0xa6afd3…d132
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity