← previous blocknext block →recent activity
Analyzing
Block #86,773,835
14 transactions · 14 stateful · 2026-07-10 05:16:03 UTC
Parallelism
57/100
Blocked
43%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,773,835 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w29w210w311w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x35d95fb0…db9e
0x34b655…2a6f
4 touches
1 conflict
0x35d95fb0…db9f
0x34b655…2a6f
4 touches
1 conflict
0x39ec8677…9e10
0x34b655…2a6f
4 touches
1 conflict
0x483f2f15…8214
0x34b655…2a6f
4 touches
1 conflict
0x5464dc08…1d39
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity