← previous blocknext block →recent activity
Analyzing
Block #87,517,949
88 transactions · 79 stateful · 2026-07-13 16:11:06 UTC
Parallelism
73/100
Blocked
81%
Avg conflicts / tx
3.47
Longest chain
24 deep
Execution timeline
did this block parallelize well?
view
block #87,517,949 · 88 txs across 24 waves · depth 24
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
wave w23
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w39w413w715w318w621w942w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
26 touches
78 conflicts
0x0733be30…112f
0x34b655…2a6f
22 touches
55 conflicts
0x00000000…0001
0xc1ff9f…b0fc
20 touches
45 conflicts
0x2c145401…09fd
0x34b655…2a6f
16 touches
28 conflicts
0x734ee320…caae
0x34b655…2a6f
14 touches
21 conflicts
0x889d5e90…929a
0x2a68ba…90c5
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x2b5101ac…090b
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
78 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity