← previous blocknext block →recent activity
Analyzing
Block #87,904,522
22 transactions · 21 stateful · 2026-07-15 11:17:21 UTC
Parallelism
50/100
Blocked
57%
Avg conflicts / tx
1.64
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,904,522 · 22 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w37w49w010w511w612w713w816w118w819w920w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfd64ea5…015c
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x59dccbd8…2bf6
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x5ce8e9ad…6207
0x34b655…2a6f
8 touches
6 conflicts
0xa0acdcf7…bd86
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 0xdfd64ea578…1e015c
Audit this contract →
← previous block·next block →recent activity