← previous blocknext block →recent activity
Analyzing
Block #90,916,150
11 transactions · 11 stateful · 2026-07-28 00:35:14 UTC
Parallelism
55/100
Blocked
36%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,916,150 · 11 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
1w02w13w24w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x0d2de0f6…e6c6
0x34b655…2a6f
4 touches
1 conflict
0xafb8e71e…9285
0x34b655…2a6f
4 touches
1 conflict
0x0db2eb69…b5e7
0x34b655…2a6f
2 touches
0 conflicts
0x1346ac01…31f2
0x34b655…2a6f
2 touches
0 conflicts
0x26dda7d6…8c4d
0x34b655…2a6f
2 touches
0 conflicts
0x3a7091da…f2eb
0x34b655…2a6f
2 touches
0 conflicts
0x4df4856c…f624
0x34b655…2a6f
2 touches
0 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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity