← previous blocknext block →recent activity
Analyzing
Block #90,853,110
21 transactions · 18 stateful · 2026-07-27 19:18:02 UTC
Parallelism
76/100
Blocked
39%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,853,110 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w06w07w18w19w210w316w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc3fc40da…1c60
0x34b655…2a6f
6 touches
3 conflicts
0x1e137b39…bae2
0x34b655…2a6f
4 touches
1 conflict
0x2fd61111…5bbc
0x34b655…2a6f
4 touches
1 conflict
0x64e5f38d…187c
0x34b655…2a6f
4 touches
1 conflict
0x8ec95f2b…f4d7
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
6 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity