← previous blocknext block →recent activity
Analyzing
Block #90,894,848
24 transactions · 18 stateful · 2026-07-27 22:48:03 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,894,848 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w07w114w016w117w218w121w322w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd676e291…3ecf
0x34b655…2a6f
8 touches
6 conflicts
0x000c0f58…f52a
0x34b655…2a6f
6 touches
3 conflicts
0x0d256389…006a
0x34b655…2a6f
6 touches
3 conflicts
0x17c3727d…cb0e
0x34b655…2a6f
6 touches
3 conflicts
0x2d651956…12e8
0x34b655…2a6f
6 touches
3 conflicts
0x303f4ecc…ab9b
0x34b655…2a6f
6 touches
3 conflicts
0x8252706a…7ca5
0x34b655…2a6f
6 touches
3 conflicts
0x94f1dd1b…79b2
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
6 conflicts on slot 0xd676e29175…2b3ecf
Audit this contract →
← previous block·next block →recent activity