← previous blocknext block →recent activity
Analyzing
Block #86,493,133
20 transactions · 18 stateful · 2026-07-08 21:57:58 UTC
Parallelism
85/100
Blocked
22%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,493,133 · 20 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
1w02w13w24w05w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51f838e5…da42
0x34b655…2a6f
6 touches
3 conflicts
0x75959b84…9bda
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xa9af5c0c…f9bc
0xd32edf…ff58
5 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x9966da31…0d0f
0x34b655…2a6f
4 touches
1 conflict
0x1fbe3441…7d6f
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
3 conflicts on slot 0x51f838e514…5eda42
Audit this contract →
← previous block·next block →recent activity