pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#112,521,228
← previous block
next block →
recent activity
Analyzing
Block #112,521,228
13 transactions · 11 stateful · 2026-10-11 16:53:04 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#112,521,228
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
0x59558d29
#3
execOrder
#4
0x5acec890
#5
execPerpOps
#6
execPerpOps
#7
withdraw
#8
execFwdPositionOpsV2
· blocks 1
#10
setData
#11
mintTo
#12
execOrders
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x23769ebc…c8ed
0x34b655…2a6f
4 touches
1 conflict
0x3153542e…32ec
0x34b655…2a6f
2 touches
0 conflicts
0x4e4da68a…2465
0x34b655…2a6f
2 touches
0 conflicts
0xaf6ee336…ac0a
0x34b655…2a6f
2 touches
0 conflicts
0xaf7f13f9…a2c9
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity