← previous blocknext block →recent activity
Analyzing
Block #87,513,168
42 transactions · 36 stateful · 2026-07-13 15:39:02 UTC
Parallelism
69/100
Blocked
67%
Avg conflicts / tx
2.38
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,513,168 · 42 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w06w17w28w010w111w212w316w317w418w519w620w721w822w926w127w729w1032w1238w1139w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x4c04ce68…d007
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0001
0xc1ff9f…b0fc
12 touches
15 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
10 touches
10 conflicts
0x69ce640b…884a
0x34b655…2a6f
10 touches
10 conflicts
0x10a5a231…be40
0x34b655…2a6f
8 touches
6 conflicts
0x2b5101ac…090b
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity