← previous blocknext block →recent activity
Analyzing
Block #87,134,366
18 transactions · 14 stateful · 2026-07-11 21:25:08 UTC
Parallelism
89/100
Blocked
14%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,134,366 · 18 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
6w07w18w09w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d9867ad…6d9a
0x34b655…2a6f
4 touches
1 conflict
0x1eb0fab5…3517
0x34b655…2a6f
4 touches
1 conflict
0x231ccc13…a7c6
0x34b655…2a6f
4 touches
1 conflict
0x28387633…e029
0x34b655…2a6f
4 touches
1 conflict
0x2ddad553…f810
0x34b655…2a6f
4 touches
1 conflict
0x3c610031…a65e
0x34b655…2a6f
4 touches
1 conflict
0x5f251b96…6054
0x34b655…2a6f
4 touches
1 conflict
0x94ba9c4a…41d8
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 0x1d9867ade5…7b6d9a
Audit this contract →
← previous block·next block →recent activity