← previous blocknext block →recent activity
Analyzing
Block #87,586,521
18 transactions · 17 stateful · 2026-07-13 23:50:20 UTC
Parallelism
56/100
Blocked
53%
Avg conflicts / tx
1.44
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,586,521 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w26w37w48w510w011w512w616w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9863393c…ce7b
0x34b655…2a6f
12 touches
15 conflicts
0xecaf4f61…7796
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x5170a218…3a84
0xc8689a…ee79
8 touches
6 conflicts
0x2e64e234…5cfa
0x34b655…2a6f
8 touches
6 conflicts
0x3a2a8323…3f40
0x34b655…2a6f
8 touches
6 conflicts
0x4d9858eb…7098
0x34b655…2a6f
8 touches
6 conflicts
0x63c900f4…2600
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
15 conflicts on slot 0x9863393ce4…4cce7b
Audit this contract →
← previous block·next block →recent activity