pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#120,063,781
← previous block
next block →
recent activity
Analyzing
Block #120,063,781
9 transactions · 7 stateful · 2026-11-07 02:43:40 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#120,063,781
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
postStateList
#3
0x6450738f
· blocks 1
#5
0x59558d29
#6
execOrders
#7
execFwdPositionOpsV2
#8
setData
#4
0x6450738f
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
0xc52e52b2…c504
0xf3fb2e…41eb
4 touches
1 conflict
0xb5157b87…7a01
0xf3fb2e…41eb
4 touches
1 conflict
0xb5157b87…7a03
0xf3fb2e…41eb
4 touches
1 conflict
0xc2575a0e…f914
0xf3fb2e…41eb
4 touches
1 conflict
0xc2575a0e…f915
0xf3fb2e…41eb
4 touches
1 conflict
0xc52e52b2…c500
0xf3fb2e…41eb
4 touches
1 conflict
0xc52e52b2…c501
0xf3fb2e…41eb
4 touches
1 conflict
0x816d0352…a531
0x254d30…93bf
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:
0xf3fb2ec6…7d41eb
1 conflict on slot
0xc52e52b2c3…5bc504
Audit this contract →
← previous block
·
next block →
recent activity