pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#112,386,768
← previous block
next block →
recent activity
Analyzing
Block #112,386,768
12 transactions · 12 stateful · 2026-10-11 05:36:33 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,386,768
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x9ac0761c
· blocks 1
#3
0x32d01e04
#4
0x59558d29
#5
0x5acec890
#6
0x928e4afa
#7
execFwdPositionOpsV2
#8
executeBatch
#9
execFwdPositionOpsV2
#10
updateDataFeedsValuesPartial
#11
setData
#2
0x9ac0761c
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94dabb65…43a3
0x34b655…2a6f
4 touches
1 conflict
0x3f14638d…888c
0xf42df8…ad97
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xccebf5c5…8758
0x34b655…2a6f
4 touches
1 conflict
0x2ba19985…9d6e
0x34b655…2a6f
4 touches
1 conflict
0x9f8eef5e…9cf5
0x34b655…2a6f
3 touches
1 conflict
0x71a9ad62…0c64
0x34b655…2a6f
3 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
1 conflict on slot
0x94dabb6529…f943a3
Audit this contract →
← previous block
·
next block →
recent activity