pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,342,609
← previous block
next block →
recent activity
Analyzing
Block #106,342,609
13 transactions · 12 stateful · 2026-09-20 02:21:20 UTC
Parallelism
85
/100
Blocked
25
%
Avg conflicts / tx
0.23
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,342,609
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execOrders
#3
0x5acec890
#4
0x5acec890
#5
0x5acec890
· blocks 2
#7
0x59558d29
· blocks 1
#9
setData
#10
execFwdPositionOpsV2
#11
forward
#6
0x5acec890
#8
0x59558d29
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w0
8
w1
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x33b7fbba…64de
0x34b655…2a6f
4 touches
1 conflict
0x25e1452b…8c3c
0x34b655…2a6f
2 touches
0 conflicts
0x3acf9416…7ddc
0x34b655…2a6f
2 touches
0 conflicts
0x757b0543…e087
0x34b655…2a6f
2 touches
0 conflicts
0x823a3658…acf6
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
0x51fc8795c8…57126f
Audit this contract →
← previous block
·
next block →
recent activity