← previous blocknext block →recent activity
Analyzing
Block #87,519,319
52 transactions · 33 stateful · 2026-07-13 16:20:21 UTC
Parallelism
69/100
Blocked
76%
Avg conflicts / tx
2.12
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,519,319 · 52 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w07w114w015w116w228w329w430w531w632w733w836w737w838w939w1040w1141w242w143w347w1248w1350w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8aef18db…9238
0x34b655…2a6f
18 touches
36 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
12 touches
15 conflicts
0x53f393fa…00b9
0x34b655…2a6f
12 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0xc36fa358…24cb
0x34b655…2a6f
10 touches
10 conflicts
0x4cabb80a…46bf
0x34b655…2a6f
10 touches
10 conflicts
0xf3d10975…0d07
0x34b655…2a6f
10 touches
10 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
36 conflicts on slot 0x8aef18dbd3…199238
Audit this contract →
← previous block·next block →recent activity