← previous blocknext block →recent activity
Analyzing
Block #86,829,839
17 transactions · 14 stateful · 2026-07-10 11:30:17 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,829,839 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w18w210w311w413w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d888c90…5479
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x1353affc…75e0
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xda20c9e9…1d26
0x34b655…2a6f
4 touches
1 conflict
0x8060f612…9559
0x34b655…2a6f
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
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
10 conflicts on slot 0x8d888c9003…aa5479
Audit this contract →
← previous block·next block →recent activity