pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#120,063,146
← previous block
next block →
recent activity
Analyzing
Block #120,063,146
12 transactions · 12 stateful · 2026-11-07 02:40:28 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#120,063,146
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x6450738f
· blocks 1
#4
0x59558d29
#5
execPerpOps
#6
execOrders
· blocks 1
#7
execFwdPositionOpsV2
#8
forward
#9
execFwdPositionOpsV2
#11
setData
#3
0x6450738f
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
6
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc52e52b2…c503
0xf3fb2e…41eb
4 touches
1 conflict
0x4fe92899…f263
0x264123…670e
4 touches
1 conflict
0xf674252c…aac0
0x264123…670e
4 touches
1 conflict
0x7c58922d…8718
0x34b655…2a6f
4 touches
1 conflict
0x85a88798…f85e
0x34b655…2a6f
4 touches
1 conflict
0xf9f8a78a…25f3
0x34b655…2a6f
4 touches
1 conflict
0x31ab7183…c600
0xf3fb2e…41eb
4 touches
1 conflict
0xc2575a0e…f914
0xf3fb2e…41eb
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…5bc503
Audit this contract →
← previous block
·
next block →
recent activity