pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,929,424
← previous block
next block →
recent activity
Analyzing
Block #86,929,424
9 transactions · 6 stateful · 2026-07-10 22:36:02 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,929,424
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 1
#5
0x3f5c179b
#6
0x0f6795d9
#7
0x6a51744a
#8
setData
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02f0ef4a…7144
0x34b655…2a6f
4 touches
1 conflict
0x7ec6c8db…23b0
0x34b655…2a6f
4 touches
1 conflict
0x2bc13458…e6d8
0x34b655…2a6f
4 touches
1 conflict
0x2bc13458…e6d9
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x6685dd01…4e45
0x34b655…2a6f
4 touches
1 conflict
0xcf504b9b…8df2
0x34b655…2a6f
4 touches
1 conflict
0xf761c023…b769
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
1 conflict on slot
0x02f0ef4ab4…c27144
Audit this contract →
← previous block
·
next block →
recent activity