pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,802,077
← previous block
next block →
recent activity
Analyzing
Block #101,802,077
8 transactions · 7 stateful · 2026-09-04 04:11:46 UTC
Parallelism
75
/100
Blocked
29
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,802,077
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
executeBatch
#3
setData
#4
execFwdPositionOpsV2
· blocks 2
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2aab0897…78f7
0x34b655…2a6f
4 touches
1 conflict
0x17acd373…ec35
0x34b655…2a6f
4 touches
1 conflict
0xe3684e08…c96a
0x34b655…2a6f
4 touches
1 conflict
0x733c7779…a647
0x34b655…2a6f
4 touches
1 conflict
0x173df5ef…3917
0x34b655…2a6f
2 touches
0 conflicts
0x375b6201…9c1e
0x34b655…2a6f
2 touches
0 conflicts
0x77e96dc5…871c
0x34b655…2a6f
2 touches
0 conflicts
0x809f2ba8…89d3
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
0x2aab08973a…f178f7
Audit this contract →
← previous block
·
next block →
recent activity