pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,814,366
← previous block
next block →
recent activity
Analyzing
Block #86,814,366
8 transactions · 7 stateful · 2026-07-10 09:46:39 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,814,366
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
#4
0x0f6795d9
· blocks 1
#6
0x6a50bff7
#7
setData
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa58f1d73…9ce0
0x34b655…2a6f
4 touches
1 conflict
0xc3e19352…2faf
0x34b655…2a6f
4 touches
1 conflict
0xcaf5a5ac…09f0
0x34b655…2a6f
4 touches
1 conflict
0xedcfbee7…ea97
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x365bd58a…0eb5
0x34b655…2a6f
4 touches
1 conflict
0x53b1efb4…c65d
0x34b655…2a6f
4 touches
1 conflict
0xa58f1d73…9ce1
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
0xa58f1d73c9…079ce0
Audit this contract →
← previous block
·
next block →
recent activity