← previous blocknext block →recent activity
Analyzing
Block #87,259,454
73 transactions · 58 stateful · 2026-07-12 11:22:21 UTC
Parallelism
71/100
Blocked
78%
Avg conflicts / tx
3.51
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #87,259,454 · 73 txs across 21 waves · depth 21
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
wave w19
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w210w212w314w415w416w524w625w752w455w556w557w659w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
30 touches
105 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0x00000000…00c9
0x34b655…2a6f
16 touches
28 conflicts
0xa39e74f7…5967
0xd32edf…ff58
15 touches
28 conflicts
0xac2a0273…721b
0x34b655…2a6f
14 touches
21 conflicts
0x737acb78…fce8
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
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
105 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity