pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#112,483,525
← previous block
next block →
recent activity
Analyzing
Block #112,483,525
11 transactions · 11 stateful · 2026-10-11 13:43:22 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#112,483,525
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0x5acec890
#3
0x5acec890
#4
0xa96df62f
#5
updatePrices
#6
execFwdPositionOpsV2
#7
0x84403c1b
· blocks 1
#9
execFwdPositionOpsV2
#10
setData
#8
0x84403c1b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e976e26…bb84
0x34b655…2a6f
4 touches
1 conflict
0x9c0e4c97…e395
0x34b655…2a6f
4 touches
1 conflict
0xce044261…45a5
0x34b655…2a6f
4 touches
1 conflict
0x0008ef72…a804
0x34b655…2a6f
4 touches
1 conflict
0x4c94c9fc…e946
0x34b655…2a6f
4 touches
1 conflict
0x1602c3c2…b624
0x34b655…2a6f
2 touches
0 conflicts
0x35eab2e5…3c0a
0x34b655…2a6f
2 touches
0 conflicts
0x4beeaa17…a32f
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
0x0e976e2646…93bb84
Audit this contract →
← previous block
·
next block →
recent activity