pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#108,419,634
← previous block
next block →
recent activity
Analyzing
Block #108,419,634
13 transactions · 11 stateful · 2026-09-27 08:38:45 UTC
Parallelism
85
/100
Blocked
18
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#108,419,634
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
0x59558d29
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x41a8f47c
#6
execFwdPositionOpsV2
#7
forward
#8
0x84403c1b
· blocks 1
#10
setData
#11
0xb70bf0…94e6
#12
execOrders
#3
0x59558d29
#9
0x84403c1b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4292a836…9ed5
0x34b655…2a6f
4 touches
1 conflict
0x899b65d2…c8cd
0x34b655…2a6f
4 touches
1 conflict
0xf3b3a6e9…8cd2
0x34b655…2a6f
4 touches
1 conflict
0xfe50dfa9…3fe4
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…0009
0x32681b…919f
2 touches
0 conflicts
0x00000000…000c
0x32681b…919f
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
0x4292a8361f…a09ed5
Audit this contract →
← previous block
·
next block →
recent activity