pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,626,983
← previous block
next block →
recent activity
Analyzing
Block #86,626,983
11 transactions · 6 stateful · 2026-07-09 12:53:55 UTC
Parallelism
82
/100
Blocked
17
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,626,983
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
multicall
#3
0x5a5d9a99
#4
0x5a5d9a99
· blocks 1
#5
updateDataFeedsValuesPartial
#7
setData
#8
0x479362…c8b5
#9
0xf9697a…1907
#10
0xe0e7ec…377d
#6
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x05f9402d…cf20
0x34b655…2a6f
2 touches
0 conflicts
0x1aea29cf…3284
0x34b655…2a6f
2 touches
0 conflicts
0x22bc4ea4…5c8a
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x2505abf0…6bac
0x34b655…2a6f
2 touches
0 conflicts
0x32b3be97…1793
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
0xfaef08b108…f90696
Audit this contract →
← previous block
·
next block →
recent activity