← previous blocknext block →recent activity
Analyzing
Block #87,719,060
21 transactions · 19 stateful · 2026-07-14 14:36:48 UTC
Parallelism
67/100
Blocked
42%
Avg conflicts / tx
0.57
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,719,060 · 21 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
4w06w17w08w19w010w212w313w416w018w519w620w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xd30f9e74…d404
0x34b655…2a6f
6 touches
3 conflicts
0x9cf82fc0…8190
0x34b655…2a6f
6 touches
3 conflicts
0xa79dadf0…437a
0x34b655…2a6f
6 touches
3 conflicts
0x4f2fabb0…9b09
0x34b655…2a6f
4 touches
1 conflict
0x6a2ebbdd…0438
0x34b655…2a6f
4 touches
1 conflict
0x6a9c1df6…1cf5
0x34b655…2a6f
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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity