← previous blocknext block →recent activity
Analyzing
Block #87,355,707
68 transactions · 58 stateful · 2026-07-12 22:05:54 UTC
Parallelism
69/100
Blocked
79%
Avg conflicts / tx
5.01
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #87,355,707 · 68 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
2w03w04w15w26w37w48w59w610w711w812w913w1014w1115w1216w1328w154w158w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
32 touches
120 conflicts
0x17c44db3…8888
0xa6afd3…d132
32 touches
120 conflicts
0x00000000…003d
0xa6afd3…d132
32 touches
120 conflicts
0xbcc5ae85…6ba2
0xa6afd3…d132
30 touches
105 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
28 touches
91 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
26 touches
78 conflicts
0x40970e69…da50
0x69df8a…6292
26 touches
78 conflicts
0xdb067026…9eb8
0x69df8a…6292
26 touches
78 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
120 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity