pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#112,171,713
← previous block
next block →
recent activity
Analyzing
Block #112,171,713
12 transactions · 12 stateful · 2026-10-10 11:34:36 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#112,171,713
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x32d01e04
#2
0x59558d29
#3
0xab083028
#4
0x5acec890
#5
0x5acec890
#6
0x5acec890
#7
execOrders
#8
execFwdPositionOpsV2
#9
0x84403c1b
· blocks 1
#11
setData
#10
0x84403c1b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x04d2ea29…6fea
0x34b655…2a6f
4 touches
1 conflict
0x77f99edc…c424
0x34b655…2a6f
4 touches
1 conflict
0xabdd2e65…212a
0x34b655…2a6f
4 touches
1 conflict
0x2f1388fc…4885
0x34b655…2a6f
4 touches
1 conflict
0x08543a4e…61bb
0x34b655…2a6f
4 touches
1 conflict
0x085df2c1…305a
0x34b655…2a6f
2 touches
0 conflicts
0x3643741b…109c
0x34b655…2a6f
2 touches
0 conflicts
0x68292fe7…d918
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
0x04d2ea29c0…816fea
Audit this contract →
← previous block
·
next block →
recent activity