pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#111,810,691
← previous block
next block →
recent activity
Analyzing
Block #111,810,691
12 transactions · 11 stateful · 2026-10-09 05:18:06 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#111,810,691
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x32d01e04
#2
0x59558d29
#3
execOrders
· blocks 1
#5
0x3e2e8792
#6
0x0c7abd22
#7
updateDataFeedsValuesPartial
#8
execFwdPositionOpsV2
#9
0x61707707
#10
0x29ff42…1fe4
#11
setData
#4
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1aa85bda…e324
0x34b655…2a6f
2 touches
0 conflicts
0x2902912b…448c
0x34b655…2a6f
2 touches
0 conflicts
0x300e902b…c42e
0x34b655…2a6f
2 touches
0 conflicts
0x32a765e4…c186
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
0xbde524f475…b143bf
Audit this contract →
← previous block
·
next block →
recent activity