← previous blocknext block →recent activity
Analyzing
Block #90,888,396
17 transactions · 16 stateful · 2026-07-27 22:15:35 UTC
Parallelism
53/100
Blocked
50%
Avg conflicts / tx
1.41
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,888,396 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w27w38w410w011w112w514w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc214e0c5…c3ae
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x310afe2c…83e1
0x34b655…2a6f
8 touches
6 conflicts
0x3c0e49c9…7833
0x34b655…2a6f
4 touches
1 conflict
0x3c4b8fbd…9354
0x34b655…2a6f
4 touches
1 conflict
0x5eb187dd…b1d6
0x34b655…2a6f
4 touches
1 conflict
0x6719a767…9d62
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
15 conflicts on slot 0xc214e0c554…45c3ae
Audit this contract →
← previous block·next block →recent activity