← previous blocknext block →recent activity
Analyzing
Block #87,716,883
35 transactions · 28 stateful · 2026-07-14 14:22:15 UTC
Parallelism
54/100
Blocked
61%
Avg conflicts / tx
3.34
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,716,883 · 35 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w09w010w113w014w115w216w317w418w519w620w721w822w923w1024w1125w1228w1329w1432w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
28 touches
91 conflicts
0x7525206c…fbd5
0x34b655…2a6f
20 touches
45 conflicts
0x5b145de0…367c
0xc8689a…ee79
16 touches
28 conflicts
0x67905f6e…02a1
0x34b655…2a6f
16 touches
28 conflicts
0xfa6e44cf…eda0
0x34b655…2a6f
16 touches
28 conflicts
0x4755fafb…859b
0x34b655…2a6f
16 touches
28 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
16 touches
28 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
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
91 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity