← previous blocknext block →recent activity
Analyzing
Block #87,617,263
19 transactions · 17 stateful · 2026-07-14 03:15:56 UTC
Parallelism
68/100
Blocked
53%
Avg conflicts / tx
1.26
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,617,263 · 19 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
2w03w04w15w26w37w49w111w213w214w318w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d94ecd9…43db
0x34b655…2a6f
10 touches
10 conflicts
0xd19c9d38…b459
0x34b655…2a6f
10 touches
10 conflicts
0xbabe821d…939b
0x34b655…2a6f
10 touches
10 conflicts
0xed59b1cd…8509
0x34b655…2a6f
10 touches
10 conflicts
0xd93edb3f…94ec
0x34b655…2a6f
10 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x91d48be7…e4e8
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
10 conflicts on slot 0x2d94ecd98c…5a43db
Audit this contract →
← previous block·next block →recent activity