← previous blocknext block →recent activity
Analyzing
Block #87,786,102
21 transactions · 19 stateful · 2026-07-14 22:05:18 UTC
Parallelism
62/100
Blocked
53%
Avg conflicts / tx
1.38
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,786,102 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w412w013w115w216w318w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9001f549…089d
0x34b655…2a6f
14 touches
21 conflicts
0x28c62bca…b746
0x34b655…2a6f
10 touches
10 conflicts
0x16898f19…955d
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x9ae859db…2d84
0x34b655…2a6f
10 touches
10 conflicts
0xc0ea76be…62e2
0x34b655…2a6f
10 touches
10 conflicts
0xec2a0a90…48b5
0x34b655…2a6f
10 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
10 touches
10 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 0x9001f5497d…54089d
Audit this contract →
← previous block·next block →recent activity