← previous blocknext block →recent activity
Analyzing
Block #86,763,821
26 transactions · 21 stateful · 2026-07-10 04:09:09 UTC
Parallelism
85/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,763,821 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w17w212w013w114w216w018w119w320w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xce827910…ff22
0x065c9d…c394
6 touches
3 conflicts
0x16c546a3…d0c3
0x34b655…2a6f
4 touches
1 conflict
0x5b79846d…5b19
0x34b655…2a6f
4 touches
1 conflict
0x778a3faa…441b
0x34b655…2a6f
4 touches
1 conflict
0x778a3faa…441c
0x34b655…2a6f
4 touches
1 conflict
0xb39cb1d8…effa
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity