← previous blocknext block →recent activity
Analyzing
Block #90,546,340
4 transactions · 4 stateful · 2026-07-26 17:34:41 UTC
Parallelism
50/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,546,340 · 4 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06df379f…2653
0x34b655…2a6f
4 touches
1 conflict
0x6a9f4a95…44e0
0x34b655…2a6f
4 touches
1 conflict
0xaafe309d…85c6
0x34b655…2a6f
4 touches
1 conflict
0x0580a071…9ec6
0x34b655…2a6f
2 touches
0 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
2 touches
0 conflicts
0x1de49243…4aa3
0x34b655…2a6f
2 touches
0 conflicts
0x20f13ae0…cca8
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
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 0x06df379f10…a22653
Audit this contract →
← previous block·next block →recent activity