← previous blocknext block →recent activity
Analyzing
Block #90,969,069
12 transactions · 11 stateful · 2026-07-28 05:01:25 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,969,069 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w210w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xdd10dbcc…19f3
0x34b655…2a6f
4 touches
1 conflict
0x7d7ff230…ccd5
0x34b655…2a6f
4 touches
1 conflict
0x9991a897…dc95
0x34b655…2a6f
4 touches
1 conflict
0x9c5ce778…4b6a
0x34b655…2a6f
4 touches
1 conflict
0xabec3222…dec0
0x34b655…2a6f
4 touches
1 conflict
0xb506a4b2…9041
0x34b655…2a6f
4 touches
1 conflict
0xc7d08bca…e210
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
3 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity