pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,407,698
← previous block
next block →
recent activity
Analyzing
Block #106,407,698
11 transactions · 10 stateful · 2026-09-20 07:48:55 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,407,698
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
0x5acec890
#4
0xab083028
#5
0x5acec890
#6
0x59558d29
#7
setData
#8
execFwdPositionOpsV2
#9
transfer
#10
0x6aaf8fe9
#3
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb8dc136f…fb16
0xc8689a…ee79
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x24c5620c…7ac5
0x34b655…2a6f
2 touches
0 conflicts
0x25bd380f…a658
0x34b655…2a6f
2 touches
0 conflicts
0x2e8ab5e2…39aa
0x34b655…2a6f
2 touches
0 conflicts
0x31c4594c…ede7
0x34b655…2a6f
2 touches
0 conflicts
0x58472b2b…640d
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: Settlement / Helper
1 conflict on slot
0xb8dc136fed…55fb16
Audit this contract →
← previous block
·
next block →
recent activity