← previous blocknext block →recent activity
Analyzing
Block #90,887,330
16 transactions · 16 stateful · 2026-07-27 22:10:14 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,887,330 · 16 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
2w04w06w17w28w29w310w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x310afe2c…83e1
0x34b655…2a6f
6 touches
3 conflicts
0x947bb79d…6458
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xec4aba77…ebf7
0x34b655…2a6f
6 touches
3 conflicts
0x6479b9ca…d2eb
0x34b655…2a6f
6 touches
3 conflicts
0xfe2577ac…677b
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity