← previous blocknext block →recent activity
Analyzing
Block #90,958,300
21 transactions · 19 stateful · 2026-07-28 04:07:13 UTC
Parallelism
62/100
Blocked
37%
Avg conflicts / tx
1.33
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,958,300 · 21 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
5w09w010w111w212w313w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xbde524f4…43bf
0x34b655…2a6f
14 touches
21 conflicts
0x705ab4ae…0162
0x34b655…2a6f
12 touches
15 conflicts
0xc197b156…b8c0
0x34b655…2a6f
5 touches
3 conflicts
0x147a19ce…dbef
0x34b655…2a6f
4 touches
1 conflict
0xa2f0b2f3…1f3b
0x34b655…2a6f
4 touches
1 conflict
0x424934c8…f2f1
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
21 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity