pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,500,318
← previous block
next block →
recent activity
Analyzing
Block #101,500,318
9 transactions · 9 stateful · 2026-09-03 02:53:51 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,500,318
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
execOrders
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOpsV2
· blocks 1
#6
forward
#7
execFwdPositionOpsV2
#8
0x6a98e1b7
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xead15497…1dbe
0x34b655…2a6f
4 touches
1 conflict
0x1659f2d1…b734
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00c43e68…2a3c
0x34b655…2a6f
2 touches
0 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x21dbdee0…d2d5
0x34b655…2a6f
2 touches
0 conflicts
0x26e65290…f011
0x34b655…2a6f
2 touches
0 conflicts
0x3817764d…242b
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
0xead15497a3…971dbe
Audit this contract →
← previous block
·
next block →
recent activity