← previous blocknext block →recent activity
Analyzing
Block #87,409,334
34 transactions · 12 stateful · 2026-07-13 04:04:36 UTC
Parallelism
85/100
Blocked
42%
Avg conflicts / tx
0.29
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,409,334 · 34 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
24w025w126w227w130w331w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x326a02b5…8dad
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x0aa5b76b…60db
0x34b655…2a6f
4 touches
1 conflict
0x0cb8d397…843e
0x34b655…2a6f
4 touches
1 conflict
0x286711a5…b3bf
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4e969cf1…4b51
0x34b655…2a6f
4 touches
1 conflict
0x5cacfb02…ef32
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 0x326a02b5c5…5c8dad
Audit this contract →
← previous block·next block →recent activity