← previous blocknext block →recent activity
Analyzing
Block #90,894,336
22 transactions · 19 stateful · 2026-07-27 22:45:28 UTC
Parallelism
68/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,894,336 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w17w08w19w210w312w413w516w517w620w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0xc467a38b…cf75
0x34b655…2a6f
6 touches
3 conflicts
0x4560e5a8…b741
0x34b655…2a6f
6 touches
3 conflicts
0x9a8af3c2…e4ae
0x34b655…2a6f
6 touches
3 conflicts
0x0d2de0f6…e6c6
0x34b655…2a6f
6 touches
3 conflicts
0x2fade833…5de4
0x34b655…2a6f
6 touches
3 conflicts
0x4db45f8c…2a9f
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity