pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,430,755
← previous block
next block →
recent activity
Analyzing
Block #106,430,755
7 transactions · 7 stateful · 2026-09-20 09:44:57 UTC
Parallelism
71
/100
Blocked
14
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,430,755
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x5acec890
· blocks 1
#4
setData
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
#3
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4a45b318…9716
0x34b655…2a6f
4 touches
1 conflict
0x74cdc294…26a8
0x34b655…2a6f
4 touches
1 conflict
0x9d6a99f9…da64
0x34b655…2a6f
4 touches
1 conflict
0xc32c7104…6608
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x238d0a65…428b
0x37db7f…ec7b
4 touches
1 conflict
0xd3d054d7…4bfb
0x37db7f…ec7b
4 touches
1 conflict
0x945d1dbe…e1d7
0xc8689a…ee79
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
0x4a45b318d4…d29716
Audit this contract →
← previous block
·
next block →
recent activity