← previous blocknext block →recent activity
Analyzing
Block #87,708,810
42 transactions · 37 stateful · 2026-07-14 13:28:04 UTC
Parallelism
60/100
Blocked
59%
Avg conflicts / tx
2.62
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,708,810 · 42 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w16w07w19w010w111w212w313w414w515w616w717w818w919w1023w229w130w338w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b818135…eff8
0x34b655…2a6f
24 touches
66 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
22 touches
55 conflicts
0x4560e5a8…b741
0x34b655…2a6f
18 touches
36 conflicts
0x5b145de0…367c
0xc8689a…ee79
16 touches
28 conflicts
0x67905f6e…02a1
0x34b655…2a6f
16 touches
28 conflicts
0x7837c02d…0965
0x34b655…2a6f
16 touches
28 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
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
66 conflicts on slot 0x8b81813549…3ceff8
Audit this contract →
← previous block·next block →recent activity