← previous blocknext block →recent activity
Analyzing
Block #87,715,141
29 transactions · 28 stateful · 2026-07-14 14:10:28 UTC
Parallelism
66/100
Blocked
61%
Avg conflicts / tx
1.97
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #87,715,141 · 29 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
2w04w05w16w07w18w29w310w411w514w215w316w617w118w220w321w122w426w727w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6389d47…9a28
0x34b655…2a6f
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x42dd9d36…3fc0
0x34b655…2a6f
10 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0x0a5529a7…492e
0x34b655…2a6f
8 touches
6 conflicts
0x26050074…6967
0x34b655…2a6f
8 touches
6 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
8 touches
6 conflicts
0xeeaba9d3…b491
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
21 conflicts on slot 0xa6389d470d…f19a28
Audit this contract →
← previous block·next block →recent activity