← previous blocknext block →recent activity
Analyzing
Block #87,725,087
30 transactions · 29 stateful · 2026-07-14 15:17:06 UTC
Parallelism
43/100
Blocked
66%
Avg conflicts / tx
4.7
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,725,087 · 30 txs across 17 waves · depth 17
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
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w26w37w48w59w610w711w812w913w1014w1115w1218w1319w1420w1525w1628w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
28 touches
91 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
26 touches
78 conflicts
0xc4de6652…13f4
0x34b655…2a6f
24 touches
66 conflicts
0xd8834cf3…0004
0x34b655…2a6f
22 touches
55 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
22 touches
55 conflicts
0x67905f6e…02a1
0x34b655…2a6f
20 touches
45 conflicts
0x5b145de0…367c
0xc8689a…ee79
20 touches
45 conflicts
0x9407f89d…82ff
0x34b655…2a6f
20 touches
45 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
91 conflicts on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity