← previous blocknext block →recent activity
Analyzing
Block #86,768,103
15 transactions · 13 stateful · 2026-07-10 04:37:45 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,768,103 · 15 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
2w08w09w110w111w212w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c7eff13…16db
0x34b655…2a6f
6 touches
3 conflicts
0xc40c8e2b…b832
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xb54c8ced…5b8c
0x34b655…2a6f
4 touches
1 conflict
0xb4c35fcd…43ae
0xa6afd3…d132
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
3 conflicts on slot 0x7c7eff130a…3f16db
Audit this contract →
← previous block·next block →recent activity