pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,663,742
← previous block
next block →
recent activity
Analyzing
Block #101,663,742
10 transactions · 9 stateful · 2026-09-03 16:35:58 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,663,742
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0x5acec890
#3
0x5acec890
#4
0x5acec890
· blocks 1
#5
0x5acec890
#6
0x59558d29
#8
increaseLoopPosition
#9
setData
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x78525272…70e3
0x34b655…2a6f
4 touches
1 conflict
0xd7ae5674…d0f2
0x34b655…2a6f
4 touches
1 conflict
0xdd18ee05…d486
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x16c911c2…e6f3
0x34b655…2a6f
2 touches
0 conflicts
0x23b2399c…6e4b
0x34b655…2a6f
2 touches
0 conflicts
0x37af32af…36c0
0x34b655…2a6f
2 touches
0 conflicts
0x38c6ff01…689f
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
0x7852527297…2070e3
Audit this contract →
← previous block
·
next block →
recent activity