pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,855,232
← previous block
next block →
recent activity
Analyzing
Block #101,855,232
10 transactions · 10 stateful · 2026-09-04 08:39:09 UTC
Parallelism
60
/100
Blocked
30
%
Avg conflicts / tx
0.4
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,855,232
· 10 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x5acec890
· blocks 2
#4
execOrders
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
#7
executeBatch
#8
setData
#2
0x5acec890
· blocks 1
#3
0x5acec890
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
9
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x0af6e2ce…75f3
0x34b655…2a6f
4 touches
1 conflict
0x2a2896a0…2a0a
0x34b655…2a6f
2 touches
0 conflicts
0x387a2497…49e1
0x34b655…2a6f
2 touches
0 conflicts
0x38855b14…b4ec
0x34b655…2a6f
2 touches
0 conflicts
0x3cf50d44…961b
0x34b655…2a6f
2 touches
0 conflicts
0x4abfb389…18f4
0x34b655…2a6f
2 touches
0 conflicts
0xa2bc9923…3304
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
3 conflicts on slot
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity