← previous blocknext block →recent activity
Analyzing
Block #87,665,703
22 transactions · 19 stateful · 2026-07-14 08:39:40 UTC
Parallelism
64/100
Blocked
53%
Avg conflicts / tx
1.68
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,665,703 · 22 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
3w04w15w26w37w49w520w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5a3b1be…8122
0x34b655…2a6f
16 touches
28 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
12 touches
15 conflicts
0x5b145de0…367c
0xc8689a…ee79
10 touches
10 conflicts
0x9fd37234…2731
0x34b655…2a6f
10 touches
10 conflicts
0x3c0c2f32…c3df
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x21c9fd73…dae4
0x34b655…2a6f
10 touches
10 conflicts
0x8d4c0bb9…ccd3
0x34b655…2a6f
10 touches
10 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
28 conflicts on slot 0xb5a3b1be7c…288122
Audit this contract →
← previous block·next block →recent activity