← previous blocknext block →recent activity
Analyzing
Block #87,409,864
19 transactions · 15 stateful · 2026-07-13 04:08:08 UTC
Parallelism
68/100
Blocked
40%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,409,864 · 19 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
1w02w13w24w35w415w016w317w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc366eef…6209
0x34b655…2a6f
10 touches
10 conflicts
0x744e0a36…70f7
0x34b655…2a6f
8 touches
6 conflicts
0x1a28e34b…1404
0x34b655…2a6f
6 touches
3 conflicts
0x20f5838c…1ce3
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x286711a5…b3bf
0x34b655…2a6f
6 touches
3 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
6 touches
3 conflicts
0x3e505a15…70f8
0x34b655…2a6f
6 touches
3 conflicts
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
10 conflicts on slot 0xfc366eef31…f06209
Audit this contract →
← previous block·next block →recent activity