← previous blocknext block →recent activity
Analyzing
Block #87,713,838
62 transactions · 52 stateful · 2026-07-14 14:01:44 UTC
Parallelism
66/100
Blocked
69%
Avg conflicts / tx
4.11
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #87,713,838 · 62 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
2w03w04w15w26w311w026w427w544w446w348w649w150w552w753w958w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
38 touches
171 conflicts
0xa6389d47…9a28
0x34b655…2a6f
22 touches
55 conflicts
0x5b145de0…367c
0xc8689a…ee79
20 touches
45 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
20 touches
45 conflicts
0x67905f6e…02a1
0x34b655…2a6f
20 touches
45 conflicts
0xd8834cf3…0004
0x34b655…2a6f
18 touches
36 conflicts
0x9407f89d…82ff
0x34b655…2a6f
18 touches
36 conflicts
0xb56f0740…7542
0x34b655…2a6f
14 touches
21 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
171 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity