pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#105,850,562
← previous block
next block →
recent activity
Analyzing
Block #105,850,562
11 transactions · 9 stateful · 2026-09-18 09:03:54 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#105,850,562
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 2
#3
0x5acec890
#4
0x59558d29
#5
0x59558d29
#7
execFwdPositionOpsV2
#8
setData
#9
execOrders
#10
execOrders
#2
0x5acec890
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x184a9b09…c825
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xcf8aa5a4…ea86
0x34b655…2a6f
4 touches
1 conflict
0x0fae022a…1a15
0x34b655…2a6f
2 touches
0 conflicts
0x24c5620c…7ac5
0x34b655…2a6f
2 touches
0 conflicts
0x27b99643…bd12
0x34b655…2a6f
2 touches
0 conflicts
0x346f634d…17e5
0x34b655…2a6f
2 touches
0 conflicts
0x39bf1238…804b
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
0x184a9b09d5…aec825
Audit this contract →
← previous block
·
next block →
recent activity