pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,969,189
← previous block
next block →
recent activity
Analyzing
Block #101,969,189
13 transactions · 11 stateful · 2026-09-04 18:15:39 UTC
Parallelism
85
/100
Blocked
27
%
Avg conflicts / tx
0.23
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,969,189
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 2
#2
execOrder
#4
0x59558d29
#5
execPerpOps
#6
execPerpOps
#7
execPerpOps
#8
setData
· blocks 1
#11
0x6a9b0b43
#12
execOrders
#3
0x928e4afa
#9
setData
#10
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
8
w0
9
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x1d4d9985…406b
0x34b655…2a6f
2 touches
0 conflicts
0x30c777f3…bacc
0x34b655…2a6f
2 touches
0 conflicts
0x33cd1d06…b945
0x34b655…2a6f
2 touches
0 conflicts
0x474b9623…8272
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
0x045532dd4b…244b7d
Audit this contract →
← previous block
·
next block →
recent activity