← previous blocknext block →recent activity
Analyzing
Block #90,994,272
13 transactions · 11 stateful · 2026-07-28 07:08:24 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,994,272 · 13 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
3w04w17w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x219c6953…c961
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xfe37a080…291a
0x34b655…2a6f
4 touches
1 conflict
0xc3a8e1d6…e816
0x34b655…2a6f
4 touches
1 conflict
0xdb44d160…960b
0x34b655…2a6f
4 touches
1 conflict
0x3df00912…7e0c
0x34b655…2a6f
2 touches
0 conflicts
0x41fc2b04…2805
0x34b655…2a6f
2 touches
0 conflicts
0x4755fafb…859b
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
1 conflict on slot 0x219c6953f3…35c961
Audit this contract →
← previous block·next block →recent activity