← previous blocknext block →recent activity
Analyzing
Block #87,754,229
25 transactions · 23 stateful · 2026-07-14 18:32:04 UTC
Parallelism
72/100
Blocked
57%
Avg conflicts / tx
1.6
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,754,229 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w59w612w113w214w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x31bda1aa…7f59
0x34b655…2a6f
10 touches
10 conflicts
0x388633a0…86cd
0x34b655…2a6f
10 touches
10 conflicts
0x5170a218…3a84
0xc8689a…ee79
10 touches
10 conflicts
0x709b98ea…4187
0x34b655…2a6f
10 touches
10 conflicts
0x70b90757…51be
0x34b655…2a6f
10 touches
10 conflicts
0x79bdf655…91f2
0x34b655…2a6f
10 touches
10 conflicts
0xa5deef6f…6c3f
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity