pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#108,960,835
← previous block
next block →
recent activity
Analyzing
Block #108,960,835
8 transactions · 6 stateful · 2026-09-29 06:07:26 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#108,960,835
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x59558d29
#3
0x5acec890
#4
execFwdPositionOpsV2
· blocks 1
#6
setData
#7
execOrders
#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
0xb874c1ad…83c9
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x07183925…5c95
0x34b655…2a6f
2 touches
0 conflicts
0x342fe47d…42ae
0x34b655…2a6f
2 touches
0 conflicts
0x3a3c1ed9…9dd5
0x34b655…2a6f
2 touches
0 conflicts
0x48719cbe…5484
0x34b655…2a6f
2 touches
0 conflicts
0x631b4113…baa9
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
0xb874c1ad90…1783c9
Audit this contract →
← previous block
·
next block →
recent activity