pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,107,027
← previous block
next block →
recent activity
Analyzing
Block #102,107,027
13 transactions · 12 stateful · 2026-09-05 05:54:28 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,107,027
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
execute
#3
0xab083028
#4
execOrders
#5
0x5acec890
#6
updateDataFeedsValuesPartial
#7
0x59558d29
#8
setData
#9
execFwdPositionOpsV2
#10
execFwdPositionOpsV2
· blocks 1
#12
0x34653439
#11
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b41d5cd…00e6
0x34b655…2a6f
4 touches
1 conflict
0xa9a9d0e0…4087
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0xf1d43917…97bf
0x34b655…2a6f
4 touches
1 conflict
0x56a284d9…32e4
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x6c28863e…840e
0x34b655…2a6f
4 touches
1 conflict
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
0x7b41d5cd10…b700e6
Audit this contract →
← previous block
·
next block →
recent activity