← previous blocknext block →recent activity
Analyzing
Block #90,790,422
27 transactions · 23 stateful · 2026-07-27 14:02:36 UTC
Parallelism
78/100
Blocked
39%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,790,422 · 27 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
6w07w18w29w013w116w217w018w119w220w321w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94ddea60…a24d
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x033cf007…136d
0x34b655…2a6f
6 touches
3 conflicts
0x379dc435…6616
0x34b655…2a6f
6 touches
3 conflicts
0xd79c9727…1233
0x34b655…2a6f
6 touches
3 conflicts
0xfc64f24b…01d1
0x34b655…2a6f
6 touches
3 conflicts
0x15653d66…d2b9
0xd32edf…ff58
5 touches
3 conflicts
0xaa9f27b0…9cf2
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 0x94ddea6064…31a24d
Audit this contract →
← previous block·next block →recent activity