← previous blocknext block →recent activity
Analyzing
Block #87,594,247
30 transactions · 27 stateful · 2026-07-14 00:42:01 UTC
Parallelism
80/100
Blocked
52%
Avg conflicts / tx
1.3
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,594,247 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w08w110w011w112w213w314w415w518w228w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42341814…60f1
0x34b655…2a6f
12 touches
15 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0xcb435a13…45a8
0x34b655…2a6f
10 touches
10 conflicts
0x5170a218…3a84
0xc8689a…ee79
8 touches
6 conflicts
0x21158693…63e2
0x34b655…2a6f
8 touches
6 conflicts
0x3ca9a061…1f41
0x34b655…2a6f
8 touches
6 conflicts
0x53ee4974…d9cc
0x34b655…2a6f
8 touches
6 conflicts
0x83d11cdf…4b92
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 0x423418147b…3460f1
Audit this contract →
← previous block·next block →recent activity