← previous blocknext block →recent activity
Analyzing
Block #87,794,360
25 transactions · 23 stateful · 2026-07-14 23:00:31 UTC
Parallelism
64/100
Blocked
48%
Avg conflicts / tx
1.72
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #87,794,360 · 25 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
6w07w18w29w310w411w512w613w714w817w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x9465204c…bf37
0x34b655…2a6f
10 touches
10 conflicts
0x98834cc0…6c23
0x34b655…2a6f
10 touches
10 conflicts
0x9ae859db…2d84
0x34b655…2a6f
10 touches
10 conflicts
0xb59b0c85…f36c
0x34b655…2a6f
10 touches
10 conflicts
0x28c62bca…b746
0x34b655…2a6f
10 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
10 touches
10 conflicts
0x7c66ee37…e599
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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity