← previous blocknext block →recent activity
Analyzing
Block #90,960,001
11 transactions · 11 stateful · 2026-07-28 04:15:47 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,960,001 · 11 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
1w03w15w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xcc58c80b…ff79
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xec3d0394…ea54
0x34b655…2a6f
4 touches
1 conflict
0x219c6953…c961
0x34b655…2a6f
2 touches
0 conflicts
0x41fc2b04…2805
0x34b655…2a6f
2 touches
0 conflicts
0x6e6b8ec7…2197
0x34b655…2a6f
2 touches
0 conflicts
0x782a5da9…15e5
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
3 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity