← previous blocknext block →recent activity
Analyzing
Block #91,125,175
21 transactions · 19 stateful · 2026-07-28 18:07:41 UTC
Parallelism
57/100
Blocked
53%
Avg conflicts / tx
1.33
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #91,125,175 · 21 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w27w38w49w310w511w615w716w820w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x176686bb…97a5
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xbc66586e…20fe
0x34b655…2a6f
6 touches
3 conflicts
0xa779293b…5e59
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x52b477bc…7ccf
0x34b655…2a6f
6 touches
3 conflicts
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
10 conflicts on slot 0x176686bb22…1c97a5
Audit this contract →
← previous block·next block →recent activity