← previous blocknext block →recent activity
Analyzing
Block #87,312,042
14 transactions · 14 stateful · 2026-07-12 17:13:55 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,312,042 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w07w18w29w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0xf321dfbc…68dc
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x25205c26…56c9
0x34b655…2a6f
4 touches
1 conflict
0x430b92ea…6f54
0x34b655…2a6f
4 touches
1 conflict
0x430b92ea…6f55
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
1 conflict on slot 0xafd867b7ed…d92b2d
Audit this contract →
← previous block·next block →recent activity