← previous blocknext block →recent activity
Analyzing
Block #87,498,476
38 transactions · 32 stateful · 2026-07-13 14:00:41 UTC
Parallelism
71/100
Blocked
56%
Avg conflicts / tx
1.71
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,498,476 · 38 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w17w09w110w011w116w017w118w219w320w421w522w623w727w232w533w634w737w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x4cabb80a…46bf
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xe4110062…caac
0x34b655…2a6f
8 touches
6 conflicts
0xf76d2451…3b31
0x34b655…2a6f
8 touches
6 conflicts
0x1716b13d…99cc
0xc8689a…ee79
8 touches
6 conflicts
0xb81fb694…2bdb
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