← previous blocknext block →recent activity
Analyzing
Block #87,714,239
32 transactions · 25 stateful · 2026-07-14 14:04:25 UTC
Parallelism
72/100
Blocked
56%
Avg conflicts / tx
1.34
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #87,714,239 · 32 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w09w110w011w112w213w314w419w220w321w524w229w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6389d47…9a28
0x34b655…2a6f
14 touches
21 conflicts
0xd8834cf3…0004
0x34b655…2a6f
10 touches
10 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
10 touches
10 conflicts
0x9407f89d…82ff
0x34b655…2a6f
10 touches
10 conflicts
0x67905f6e…02a1
0x34b655…2a6f
10 touches
10 conflicts
0xab5ba139…ea6f
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