← previous blocknext block →recent activity
Analyzing
Block #86,502,773
24 transactions · 21 stateful · 2026-07-08 23:02:16 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,502,773 · 24 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
1w04w06w110w114w016w020w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xded7831c…3c4a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0xa42e8482…b88f
0x34b655…2a6f
4 touches
1 conflict
0xa7e45018…b59c
0x34b655…2a6f
4 touches
1 conflict
0x36890fff…f3d1
0x34b655…2a6f
4 touches
1 conflict
0x7c0bdc54…9dde
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0xded7831cbc…d33c4a
Audit this contract →
← previous block·next block →recent activity