← previous blocknext block →recent activity
Analyzing
Block #87,512,813
25 transactions · 23 stateful · 2026-07-13 15:36:40 UTC
Parallelism
68/100
Blocked
48%
Avg conflicts / tx
1.32
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,512,813 · 25 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
1w03w07w08w19w210w311w412w313w114w415w519w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8cf1f868…c5af
0x34b655…2a6f
12 touches
15 conflicts
0x8e507257…71c1
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x13c5b486…d41e
0x34b655…2a6f
10 touches
10 conflicts
0x0858f559…2477
0x34b655…2a6f
8 touches
6 conflicts
0xe57232b3…0fbf
0x34b655…2a6f
8 touches
6 conflicts
0x157dbfb2…4089
0x34b655…2a6f
8 touches
6 conflicts
0x18e900fa…07f4
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
15 conflicts on slot 0x8cf1f86890…38c5af
Audit this contract →
← previous block·next block →recent activity