← previous blocknext block →recent activity
Analyzing
Block #87,786,420
32 transactions · 30 stateful · 2026-07-14 22:07:25 UTC
Parallelism
44/100
Blocked
70%
Avg conflicts / tx
4.03
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #87,786,420 · 32 txs across 18 waves · depth 18
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w07w29w310w411w512w613w714w815w916w1018w1119w323w1227w1428w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9001f549…089d
0x34b655…2a6f
26 touches
78 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
20 touches
45 conflicts
0xd19c9d38…b459
0x34b655…2a6f
18 touches
36 conflicts
0x5b145de0…367c
0xc8689a…ee79
16 touches
28 conflicts
0x28c62bca…b746
0x34b655…2a6f
16 touches
28 conflicts
0x9599eb41…b5d6
0x34b655…2a6f
16 touches
28 conflicts
0x9ae859db…2d84
0x34b655…2a6f
16 touches
28 conflicts
0x5597fdd8…3f39
0x34b655…2a6f
12 touches
15 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
78 conflicts on slot 0x9001f5497d…54089d
Audit this contract →
← previous block·next block →recent activity