pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#105,574,807
← previous block
next block →
recent activity
Analyzing
Block #105,574,807
10 transactions · 10 stateful · 2026-09-17 09:54:31 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#105,574,807
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
execOrders
#3
0xab083028
#4
0x5acec890
#6
0x59558d29
#7
setData
#8
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
#5
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4de0b2a2…784f
0xc8689a…ee79
4 touches
1 conflict
0x8afdadd3…abba
0x34b655…2a6f
4 touches
1 conflict
0x8e512ac1…ddf0
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd1e80b4f…8d99
0x34b655…2a6f
4 touches
1 conflict
0xf4e7cb84…69de
0x34b655…2a6f
4 touches
1 conflict
0x235b6aa7…ec37
0x37db7f…ec7b
4 touches
1 conflict
0x47c4f650…509c
0x37db7f…ec7b
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: Settlement / Helper
1 conflict on slot
0x4de0b2a2dc…5e784f
Audit this contract →
← previous block
·
next block →
recent activity