pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#111,830,309
← previous block
next block →
recent activity
Analyzing
Block #111,830,309
12 transactions · 11 stateful · 2026-10-09 06:56:49 UTC
Parallelism
75
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#111,830,309
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x59558d29
#2
execOrders
· blocks 1
#4
updatePrices
#5
0x5acec890
#6
updatePrices
#8
setData
#9
execOrders
#10
0xc58eae…4e7b
#11
execOrders
#3
execOrders
· blocks 1
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99601df7…7339
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x08dd7039…f1c5
0x34b655…2a6f
2 touches
0 conflicts
0x0fcb5a25…9f42
0x34b655…2a6f
2 touches
0 conflicts
0x12df0148…6873
0x34b655…2a6f
2 touches
0 conflicts
0x1991b202…d120
0x34b655…2a6f
2 touches
0 conflicts
0x1cc89ad2…8e02
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
0x99601df757…887339
Audit this contract →
← previous block
·
next block →
recent activity