← previous blocknext block →recent activity
Analyzing
Block #90,887,063
24 transactions · 19 stateful · 2026-07-27 22:08:53 UTC
Parallelism
79/100
Blocked
37%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,887,063 · 24 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
6w07w19w010w111w214w318w420w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x033cf007…136d
0x34b655…2a6f
8 touches
6 conflicts
0x6479b9ca…d2eb
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x3b6e959d…158f
0x34b655…2a6f
4 touches
1 conflict
0x45e9bcf8…87e2
0x34b655…2a6f
4 touches
1 conflict
0x519e0fef…7303
0x34b655…2a6f
4 touches
1 conflict
0x55898fed…c787
0x34b655…2a6f
4 touches
1 conflict
0x6a274df0…6879
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 0x033cf007c8…d2136d
Audit this contract →
← previous block·next block →recent activity