pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,242,770
← previous block
next block →
recent activity
Analyzing
Block #102,242,770
8 transactions · 8 stateful · 2026-09-05 17:22:24 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,242,770
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
updateDataFeedsValuesPartial
#3
0x59558d29
#4
setData
#5
execFwdPositionOpsV2
· blocks 2
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07d94be1…7fa8
0x34b655…2a6f
4 touches
1 conflict
0x81c7b767…2d6d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x09c18b77…e322
0x34b655…2a6f
2 touches
0 conflicts
0x0ec07cf7…c0c9
0x34b655…2a6f
2 touches
0 conflicts
0x32e1d03e…68a7
0x34b655…2a6f
2 touches
0 conflicts
0x3a02129f…9eaf
0x34b655…2a6f
2 touches
0 conflicts
0x448fdf2a…fab4
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
0x07d94be17c…6a7fa8
Audit this contract →
← previous block
·
next block →
recent activity