← previous blocknext block →recent activity
Analyzing
Block #87,579,374
23 transactions · 18 stateful · 2026-07-13 23:02:32 UTC
Parallelism
83/100
Blocked
56%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,579,374 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w08w19w210w313w114w015w117w218w122w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x830b63a6…8105
0x34b655…2a6f
8 touches
6 conflicts
0x54526994…55b2
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x6ba04105…896f
0x34b655…2a6f
6 touches
3 conflicts
0xc5fb66df…141f
0xd32edf…ff58
5 touches
3 conflicts
0x872e51c8…ae27
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0x830b63a692…148105
Audit this contract →
← previous block·next block →recent activity