pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,097,601
← previous block
next block →
recent activity
Analyzing
Block #102,097,601
10 transactions · 9 stateful · 2026-09-05 05:06:38 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,097,601
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x8263f5d9
#3
0x59558d29
#4
execPerpOps
· blocks 1
#6
setData
#7
forward
#8
execFwdPositionOpsV2
· blocks 1
#5
execPerpOps
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xafb22303…6db2
0x34b655…2a6f
4 touches
1 conflict
0xafb22303…6db3
0x34b655…2a6f
4 touches
1 conflict
0x3b305cd3…42eb
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0x88b76cfd…ef2b
0x34b655…2a6f
3 touches
1 conflict
0x051282a6…90dc
0x34b655…2a6f
3 touches
1 conflict
0x09106a95…1467
0x33176b…e078
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
0xbcbf5d09a8…c68bac
Audit this contract →
← previous block
·
next block →
recent activity