← previous blocknext block →recent activity
Analyzing
Block #87,645,879
41 transactions · 34 stateful · 2026-07-14 06:27:11 UTC
Parallelism
61/100
Blocked
68%
Avg conflicts / tx
2.63
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,645,879 · 41 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
1w02w15w29w010w111w212w013w114w215w316w417w518w619w720w821w922w1023w1124w1228w1335w136w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
26 touches
78 conflicts
0xb5a3b1be…8122
0x34b655…2a6f
12 touches
15 conflicts
0xa37d59c6…996b
0x34b655…2a6f
12 touches
15 conflicts
0x4560e5a8…b741
0x34b655…2a6f
10 touches
10 conflicts
0x487aa334…7ef2
0x34b655…2a6f
10 touches
10 conflicts
0x49f75237…44f4
0x34b655…2a6f
10 touches
10 conflicts
0x7837c02d…0965
0x34b655…2a6f
10 touches
10 conflicts
0x8b46e9d1…e148
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
78 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity