← previous blocknext block →recent activity
Analyzing
Block #90,222,060
13 transactions · 11 stateful · 2026-07-25 14:08:20 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,222,060 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w18w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0x0181bb37…6629
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x17c24c5b…471c
0x34b655…2a6f
4 touches
1 conflict
0x43a02937…4672
0x34b655…2a6f
4 touches
1 conflict
0x4d1c2806…5947
0x34b655…2a6f
4 touches
1 conflict
0x54001736…3833
0x34b655…2a6f
4 touches
1 conflict
0x729817ff…f2fd
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 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity