← previous blocknext block →recent activity
Analyzing
Block #87,714,265
43 transactions · 36 stateful · 2026-07-14 14:04:35 UTC
Parallelism
70/100
Blocked
67%
Avg conflicts / tx
1.74
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,714,265 · 43 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
2w04w15w06w17w210w011w112w013w114w218w219w320w421w522w623w730w332w133w834w237w338w340w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
12 touches
15 conflicts
0xa56e54d0…2d39
0x34b655…2a6f
10 touches
10 conflicts
0x767799cd…f423
0xc8689a…ee79
8 touches
6 conflicts
0x0f8965bb…e238
0x34b655…2a6f
8 touches
6 conflicts
0x1aa5ecc1…1b3d
0x34b655…2a6f
8 touches
6 conflicts
0x880fc665…31e3
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
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