← previous blocknext block →recent activity
Analyzing
Block #87,579,474
24 transactions · 20 stateful · 2026-07-13 23:03:12 UTC
Parallelism
79/100
Blocked
50%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,579,474 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w29w110w212w313w414w015w121w122w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cfbc6b1…2649
0x34b655…2a6f
8 touches
6 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x71cd2af8…dbd4
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0x4cfbc6b1c8…d22649
Audit this contract →
← previous block·next block →recent activity