← previous blocknext block →recent activity
Analyzing
Block #86,971,386
16 transactions · 15 stateful · 2026-07-11 03:16:28 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,971,386 · 16 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
1w05w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x615b36e9…e79c
0x34b655…2a6f
4 touches
1 conflict
0x89c4fedf…b214
0x34b655…2a6f
4 touches
1 conflict
0x89c4fedf…b215
0x34b655…2a6f
4 touches
1 conflict
0x072c4867…c7a9
0x34b655…2a6f
4 touches
1 conflict
0xc5e55770…12e8
0x34b655…2a6f
4 touches
1 conflict
0xc5e55770…12e9
0x34b655…2a6f
4 touches
1 conflict
0xdb89ef9a…606c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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 0x615b36e9bd…4fe79c
Audit this contract →
← previous block·next block →recent activity