← previous blocknext block →recent activity
Analyzing
Block #91,253,520
20 transactions · 18 stateful · 2026-07-29 04:53:22 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
0.9
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,253,520 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w412w514w615w718w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a0cecef…4ed0
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x07d8b1e8…78c6
0x34b655…2a6f
6 touches
3 conflicts
0x35b0198e…3e0d
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x56a9f59c…681d
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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
10 conflicts on slot 0x0a0cecef55…324ed0
Audit this contract →
← previous block·next block →recent activity