← previous blocknext block →recent activity
Analyzing
Block #90,770,908
18 transactions · 17 stateful · 2026-07-27 12:24:23 UTC
Parallelism
56/100
Blocked
59%
Avg conflicts / tx
1.72
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,770,908 · 18 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
1w02w15w07w28w19w211w212w313w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d10975…0d07
0x34b655…2a6f
16 touches
28 conflicts
0xea02471d…1542
0x34b655…2a6f
16 touches
28 conflicts
0x4bc1abab…5874
0x34b655…2a6f
12 touches
15 conflicts
0xbde524f4…43bf
0x34b655…2a6f
12 touches
15 conflicts
0xb1849477…ecff
0x34b655…2a6f
7 touches
6 conflicts
0xdb780694…a2f0
0x34b655…2a6f
7 touches
6 conflicts
0x7103efb2…75cd
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
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
28 conflicts on slot 0xf3d10975b0…050d07
Audit this contract →
← previous block·next block →recent activity