← previous blocknext block →recent activity
Analyzing
Block #86,632,651
18 transactions · 14 stateful · 2026-07-09 13:31:51 UTC
Parallelism
89/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,632,651 · 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
2w03w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4e9800f…4ab0
0x34b655…2a6f
4 touches
1 conflict
0xe5a38e46…a68c
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab1
0x34b655…2a6f
4 touches
1 conflict
0x159cff26…7665
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x585cfb2c…2e9f
0x34b655…2a6f
2 touches
0 conflicts
0x5bb46f6c…7693
0x34b655…2a6f
2 touches
0 conflicts
0x5f72d58f…c445
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
1 conflict on slot 0xa4e9800f4e…fc4ab0
Audit this contract →
← previous block·next block →recent activity