← previous blocknext block →recent activity
Analyzing
Block #87,703,714
38 transactions · 37 stateful · 2026-07-14 12:53:56 UTC
Parallelism
74/100
Blocked
51%
Avg conflicts / tx
1.32
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #87,703,714 · 38 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
1w02w13w24w35w49w010w111w212w313w414w518w232w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x8fe37a3f…4c89
0x34b655…2a6f
10 touches
10 conflicts
0xae9bf37b…612b
0xd32edf…ff58
9 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x67905f6e…02a1
0x34b655…2a6f
8 touches
6 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0x4f51d069…d0b4
0x34b655…2a6f
8 touches
6 conflicts
0x7ae94b74…7aef
0x34b655…2a6f
8 touches
6 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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity