← previous blocknext block →recent activity
Analyzing
Block #87,700,172
119 transactions · 57 stateful · 2026-07-14 12:30:04 UTC
Parallelism
84/100
Blocked
79%
Avg conflicts / tx
2.26
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #87,700,172 · 119 txs across 19 waves · depth 19
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
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w210w213w316w419w522w624w727w828w929w1031w1133w1234w1335w1444w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
28 touches
91 conflicts
0x92385428…6941
0x34b655…2a6f
26 touches
78 conflicts
0x889d5e90…929a
0x2a68ba…90c5
22 touches
55 conflicts
0xe116ff14…5038
0xd32edf…ff58
19 touches
45 conflicts
0x482471ad…122f
0x34b655…2a6f
18 touches
36 conflicts
0xb3fb9fb5…64dc
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x0733be30…112f
0x34b655…2a6f
16 touches
28 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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity