← previous blocknext block →recent activity
Analyzing
Block #87,586,336
24 transactions · 18 stateful · 2026-07-13 23:49:06 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
1.17
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,586,336 · 24 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
1w04w07w08w19w212w313w414w515w617w122w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f34fd08…aeb3
0x34b655…2a6f
10 touches
10 conflicts
0x7c6a17fa…e95d
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x745952b2…d90c
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x2f3fc042…4567
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x5f34fd08e4…a5aeb3
Audit this contract →
← previous block·next block →recent activity