← previous blocknext block →recent activity
Analyzing
Block #87,046,013
9 transactions · 9 stateful · 2026-07-11 11:35:10 UTC
Parallelism
78/100
Blocked
22%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,046,013 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ff8b157…106c
0x34b655…2a6f
4 touches
1 conflict
0x278676c0…d15c
0x34b655…2a6f
4 touches
1 conflict
0x2c2761c0…476e
0x34b655…2a6f
4 touches
1 conflict
0x43e15ca4…039d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x482f3ed7…3307
0x34b655…2a6f
4 touches
1 conflict
0x482f3ed7…3308
0x34b655…2a6f
4 touches
1 conflict
0x5a19ef35…dc70
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 0x0ff8b15712…06106c
Audit this contract →
← previous block·next block →recent activity