← previous blocknext block →recent activity
Analyzing
Block #87,584,960
13 transactions · 12 stateful · 2026-07-13 23:39:54 UTC
Parallelism
54/100
Blocked
58%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,584,960 · 13 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
1w02w13w04w15w17w28w310w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17cc5ec3…ae0e
0x34b655…2a6f
6 touches
3 conflicts
0x4a559be0…1f90
0x34b655…2a6f
6 touches
3 conflicts
0x5d2f0b01…112a
0x34b655…2a6f
6 touches
3 conflicts
0x4467ecee…e95b
0x34b655…2a6f
6 touches
3 conflicts
0x63f8a50d…333b
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xd2453506…54e4
0x34b655…2a6f
6 touches
3 conflicts
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
3 conflicts on slot 0x17cc5ec39e…57ae0e
Audit this contract →
← previous block·next block →recent activity