← previous blocknext block →recent activity
Analyzing
Block #90,552,603
7 transactions · 6 stateful · 2026-07-26 18:06:11 UTC
Parallelism
57/100
Blocked
50%
Avg conflicts / tx
0.57
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,552,603 · 7 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
2w03w14w26w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b6af007…0f35
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xfaa5c672…5681
0x34b655…2a6f
4 touches
1 conflict
0x1a5d321d…a474
0x34b655…2a6f
4 touches
1 conflict
0x78255c70…2734
0x34b655…2a6f
4 touches
1 conflict
0x85c8557c…8795
0x34b655…2a6f
4 touches
1 conflict
0x9737fb40…d8cb
0x34b655…2a6f
4 touches
1 conflict
0xc5570577…8bf0
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 0x5b6af0070f…160f35
Audit this contract →
← previous block·next block →recent activity