pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,155,657
← previous block
next block →
recent activity
Analyzing
Block #86,155,657
11 transactions · 9 stateful · 2026-07-07 08:23:39 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,155,657
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updatePrices
#3
0x39435dac
· blocks 1
#5
updateDataFeedsValuesPartial
#6
approve
#7
batchUpdate
#8
0x0f6795d9
#9
setData
#10
0x39435dac
#4
0x39435dac
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
0xde398ff4…00ca
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x4d8a8821…df85
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0x212243c5…f412
0x34b655…2a6f
4 touches
1 conflict
0x472d25ae…5215
0x34b655…2a6f
2 touches
0 conflicts
0x577e9a2a…3561
0x34b655…2a6f
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
1 conflict on slot
0xde398ff412…a000ca
Audit this contract →
← previous block
·
next block →
recent activity