pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#120,069,651
← previous block
next block →
recent activity
Analyzing
Block #120,069,651
11 transactions · 9 stateful · 2026-11-07 03:13:19 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
#120,069,651
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6450738f
#2
0x6450738f
· blocks 1
#4
execOrders
#5
updatePrices
#6
updatePrices
#7
0x57368ddf
#8
updateDataFeedsValuesPartial
#9
setData
#10
execute
#3
0x6450738f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8526d50…eadc
0x264123…670e
4 touches
1 conflict
0x816d0352…a531
0x9cd7a2…d1a8
4 touches
1 conflict
0x69db23d3…ca80
0xae8e0c…e422
4 touches
1 conflict
0xc2575a0e…0f80
0xae8e0c…e422
4 touches
1 conflict
0xca30c963…0280
0xae8e0c…e422
4 touches
1 conflict
0xca30c963…0281
0xae8e0c…e422
4 touches
1 conflict
0xca30c963…0282
0xae8e0c…e422
4 touches
1 conflict
0x7003a7a5…94b5
0x264123…670e
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:
0x264123a9…fa670e
1 conflict on slot
0xc8526d50f8…a1eadc
Audit this contract →
← previous block
·
next block →
recent activity