← previous blocknext block →recent activity
Analyzing
Block #87,662,181
56 transactions · 46 stateful · 2026-07-14 08:16:07 UTC
Parallelism
70/100
Blocked
78%
Avg conflicts / tx
3.41
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,662,181 · 56 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
3w04w15w07w18w29w311w012w113w014w115w217w318w420w121w222w323w436w237w541w1242w144w245w446w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
32 touches
120 conflicts
0x08330b36…ae29
0x34b655…2a6f
12 touches
15 conflicts
0xafb2524a…0ce4
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0001
0xc1ff9f…b0fc
10 touches
10 conflicts
0x5170a218…3a84
0xc8689a…ee79
10 touches
10 conflicts
0x6d42d870…6630
0x34b655…2a6f
8 touches
6 conflicts
0x75b43fdd…8dc1
0x34b655…2a6f
8 touches
6 conflicts
0x80eee30b…e801
0x34b655…2a6f
8 touches
6 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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity