← previous blocknext block →recent activity
Analyzing
Block #87,625,314
28 transactions · 27 stateful · 2026-07-14 04:09:45 UTC
Parallelism
64/100
Blocked
52%
Avg conflicts / tx
1.75
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #87,625,314 · 28 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
4w05w17w08w29w310w411w512w613w717w120w221w323w826w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x08330b36…ae29
0x34b655…2a6f
14 touches
21 conflicts
0x2d94ecd9…43db
0x34b655…2a6f
12 touches
15 conflicts
0x167de262…f61f
0x34b655…2a6f
12 touches
15 conflicts
0x9599eb41…b5d6
0x34b655…2a6f
12 touches
15 conflicts
0x2fade833…5de4
0x34b655…2a6f
11 touches
15 conflicts
0x75b43fdd…8dc1
0x34b655…2a6f
11 touches
15 conflicts
0x5b145de0…367c
0xc8689a…ee79
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity