pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,894,414
← previous block
next block →
recent activity
Analyzing
Block #101,894,414
8 transactions · 6 stateful · 2026-09-04 11:56:24 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,894,414
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
0x6a9ab260
#3
withdraw
#4
execFwdPositionOpsV2
· blocks 1
#6
setData
#7
execOrders
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e3014f0…b4e1
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x81878590…6d25
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x574628e9…dcc3
0x34b655…2a6f
2 touches
0 conflicts
0x641aed07…bcb9
0x34b655…2a6f
2 touches
0 conflicts
0x82dd2252…e1ce
0x34b655…2a6f
2 touches
0 conflicts
0x9816fc81…4f3c
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
0x5e3014f0c7…b1b4e1
Audit this contract →
← previous block
·
next block →
recent activity