← previous blocknext block →recent activity
Analyzing
Block #87,711,262
20 transactions · 18 stateful · 2026-07-14 13:44:28 UTC
Parallelism
65/100
Blocked
44%
Avg conflicts / tx
0.8
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,711,262 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w07w110w111w212w315w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e088aaa…3972
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x8fe37a3f…4c89
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x013a6b08…d120
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0001
0xc1ff9f…b0fc
4 touches
1 conflict
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
3 conflicts on slot 0x6e088aaa5c…d43972
Audit this contract →
← previous block·next block →recent activity