← previous blocknext block →recent activity
Analyzing
Block #87,724,305
21 transactions · 19 stateful · 2026-07-14 15:11:52 UTC
Parallelism
52/100
Blocked
58%
Avg conflicts / tx
2.19
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #87,724,305 · 21 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
1w03w04w15w26w37w48w59w612w113w714w817w919w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x9eb155db…f714
0x34b655…2a6f
12 touches
15 conflicts
0x5170a218…3a84
0xc8689a…ee79
10 touches
10 conflicts
0x44d214fe…4f5e
0x34b655…2a6f
10 touches
10 conflicts
0x4efc76b1…9b56
0x34b655…2a6f
10 touches
10 conflicts
0x709b98ea…4187
0x34b655…2a6f
10 touches
10 conflicts
0x79bdf655…91f2
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity