← previous blocknext block →recent activity
Analyzing
Block #87,904,849
30 transactions · 29 stateful · 2026-07-15 11:19:32 UTC
Parallelism
67/100
Blocked
52%
Avg conflicts / tx
1.33
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #87,904,849 · 30 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w08w09w110w212w313w114w115w316w417w518w622w223w728w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x067c61b8…650f
0x34b655…2a6f
12 touches
15 conflicts
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x59dccbd8…2bf6
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x0dd44476…ef40
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
15 conflicts on slot 0x067c61b803…d7650f
Audit this contract →
← previous block·next block →recent activity