← previous blocknext block →recent activity
Analyzing
Block #86,620,856
8 transactions · 7 stateful · 2026-07-09 12:13:02 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,620,856 · 8 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1aa
0xb1dbf0…c0d3
6 touches
3 conflicts
0x8a35acfb…d1ab
0xb1dbf0…c0d3
6 touches
3 conflicts
0x7f430e47…4cbd
0xb1dbf0…c0d3
3 touches
1 conflict
0x6c68ddc9…d106
0xb1dbf0…c0d3
3 touches
1 conflict
0x143dba04…1b98
0xb1dbf0…c0d3
3 touches
1 conflict
0x1e451306…7993
0xb1dbf0…c0d3
3 touches
1 conflict
0x2e9e299b…9e04
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity