← previous blocknext block →recent activity
Analyzing
Block #86,980,013
14 transactions · 12 stateful · 2026-07-11 04:14:02 UTC
Parallelism
64/100
Blocked
42%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,980,013 · 14 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
4w06w17w28w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x6c7e1952…d9c9
0x34b655…2a6f
10 touches
10 conflicts
0x33c7a9e0…4810
0x34b655…2a6f
6 touches
3 conflicts
0x36890fff…f3d1
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49a97bff…33ed
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09c
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
10 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity