← previous blocknext block →recent activity
Analyzing
Block #90,463,592
14 transactions · 14 stateful · 2026-07-26 10:38:24 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,463,592 · 14 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
1w02w13w05w06w17w210w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a5d321d…a474
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x603fba44…4155
0x34b655…2a6f
6 touches
3 conflicts
0x0933b65e…e7d4
0x34b655…2a6f
6 touches
3 conflicts
0x65752137…fb57
0x34b655…2a6f
6 touches
3 conflicts
0x803cd43b…b348
0x34b655…2a6f
6 touches
3 conflicts
0x890d1628…b8f7
0x34b655…2a6f
6 touches
3 conflicts
0x8a02d049…f481
0x34b655…2a6f
6 touches
3 conflicts
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
10 conflicts on slot 0x1a5d321d5d…0da474
Audit this contract →
← previous block·next block →recent activity