← previous blocknext block →recent activity
Analyzing
Block #87,700,267
91 transactions · 43 stateful · 2026-07-14 12:30:42 UTC
Parallelism
82/100
Blocked
74%
Avg conflicts / tx
1.14
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,700,267 · 91 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
1w02w13w24w05w09w110w111w114w215w316w417w518w619w368w269w376w477w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x889d5e90…929a
0x2a68ba…90c5
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xf7640726…19a2
0x2a68ba…90c5
12 touches
15 conflicts
0x8649e48f…941c
0xc8689a…ee79
10 touches
10 conflicts
0x915c095e…c1e5
0x2b46c0…1669
10 touches
10 conflicts
0xcfe06a18…b5b5
0x2b46c0…1669
10 touches
10 conflicts
0xd8fd2add…50fc
0x2b46c0…1669
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity