← previous blocknext block →recent activity
Analyzing
Block #87,586,943
22 transactions · 19 stateful · 2026-07-13 23:53:09 UTC
Parallelism
73/100
Blocked
53%
Avg conflicts / tx
0.82
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,586,943 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w06w19w110w212w313w114w220w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3560a56c…d95d
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0xdf39e0b5…6504
0x34b655…2a6f
6 touches
3 conflicts
0x176771f9…c1a4
0x34b655…2a6f
4 touches
1 conflict
0x1a1df941…41d5
0x34b655…2a6f
4 touches
1 conflict
0x1c5d445b…7a6c
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 0x3560a56c3c…9cd95d
Audit this contract →
← previous block·next block →recent activity