← previous blocknext block →recent activity
Analyzing
Block #87,735,836
49 transactions · 39 stateful · 2026-07-14 16:29:01 UTC
Parallelism
67/100
Blocked
56%
Avg conflicts / tx
1.45
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,735,836 · 49 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w06w17w28w09w110w018w019w120w221w322w423w524w625w726w830w131w934w135w236w1037w1139w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x9001f549…089d
0x34b655…2a6f
10 touches
10 conflicts
0x22e7ebfe…1293
0x34b655…2a6f
8 touches
6 conflicts
0x26050074…6967
0x34b655…2a6f
8 touches
6 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0x077d58c3…8ed7
0x34b655…2a6f
8 touches
6 conflicts
0x58620f29…db5a
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity