← previous blocknext block →recent activity
Analyzing
Block #86,335,779
10 transactions · 6 stateful · 2026-07-08 04:26:22 UTC
Parallelism
80/100
Blocked
17%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,335,779 · 10 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0x56f2040f…3e43
0x34b655…2a6f
3 touches
1 conflict
0x084104fa…cd5c
0x34b655…2a6f
2 touches
0 conflicts
0x17f9dcd0…bb6b
0x34b655…2a6f
2 touches
0 conflicts
0x1cb2ff43…5e78
0x34b655…2a6f
2 touches
0 conflicts
0x1e7e4246…4872
0x34b655…2a6f
2 touches
0 conflicts
0x32cfcaed…9b9b
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 0xe06bbb2ef5…889417
Audit this contract →
← previous block·next block →recent activity