pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#108,676,684
← previous block
next block →
recent activity
Analyzing
Block #108,676,684
11 transactions · 11 stateful · 2026-09-28 06:13:03 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#108,676,684
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
setData
#3
0x59558d29
#4
execOrders
#5
execFwdPositionOpsV2
#6
execOrders
· blocks 1
#7
updateDataFeedsValuesPartial
#8
0x61d59c2d
#10
execute
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x2c1f5f37…b898
0x065c9d…c394
2 touches
0 conflicts
0x2d976aa2…c7ec
0x065c9d…c394
2 touches
0 conflicts
0x6e0a9178…76f7
0x065c9d…c394
2 touches
0 conflicts
0xae83f89c…d9ad
0x065c9d…c394
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity