pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#112,338,409
← previous block
next block →
recent activity
Analyzing
Block #112,338,409
12 transactions · 9 stateful · 2026-10-11 01:33:16 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#112,338,409
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x59558d29
#3
execOrders
· blocks 1
#4
execOrders
#6
increase
#7
updateDataFeedsValuesPartial
#8
execFwdPositionOpsV2
#9
executeBatch
#10
0x57368ddf
#11
setData
#5
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
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
0x0008ef72…a804
0x34b655…2a6f
2 touches
0 conflicts
0x08527e66…b051
0x34b655…2a6f
2 touches
0 conflicts
0x1807763c…6c7c
0x34b655…2a6f
2 touches
0 conflicts
0x1b5989b4…4dbf
0x34b655…2a6f
2 touches
0 conflicts
0x2ac4cf3c…ec38
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