← previous blocknext block →recent activity
Analyzing
Block #87,712,094
67 transactions · 52 stateful · 2026-07-14 13:50:02 UTC
Parallelism
66/100
Blocked
69%
Avg conflicts / tx
4.12
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #87,712,094 · 67 txs across 23 waves · depth 23
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
wave w21
wave w22
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w16w27w08w29w310w411w512w658w263w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
40 touches
190 conflicts
0xa6389d47…9a28
0x34b655…2a6f
18 touches
36 conflicts
0x5b145de0…367c
0xc8689a…ee79
16 touches
28 conflicts
0x67905f6e…02a1
0x34b655…2a6f
16 touches
28 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
16 touches
28 conflicts
0x3b9bb58c…e73a
0x34b655…2a6f
14 touches
21 conflicts
0x889d5e90…929a
0x2a68ba…90c5
12 touches
15 conflicts
0x1be49a4e…3c50
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
190 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity