← previous blocknext block →recent activity
Analyzing
Block #86,853,052
26 transactions · 22 stateful · 2026-07-10 14:05:25 UTC
Parallelism
77/100
Blocked
32%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,853,052 · 26 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w18w010w011w117w218w321w322w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc788862c…c259
0x34b655…2a6f
8 touches
6 conflicts
0x28f324ed…9db7
0x34b655…2a6f
6 touches
3 conflicts
0x8df5fa2c…02e6
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x42d8b371…bb43
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x94ba9c4a…41d8
0x34b655…2a6f
4 touches
1 conflict
0xa2dd7133…24d0
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
6 conflicts on slot 0xc788862c2e…6ec259
Audit this contract →
← previous block·next block →recent activity