pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#112,485,461
← previous block
next block →
recent activity
Analyzing
Block #112,485,461
11 transactions · 9 stateful · 2026-10-11 13:53:07 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#112,485,461
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x9ac0761c
· blocks 2
#3
0x59558d29
#4
execPerpOps
#5
execPerpOps
#6
execOrders
#7
updateDataFeedsValuesPartial
#9
setData
#10
0x0c7abd22
#2
0x9ac0761c
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8c211514…b757
0x34b655…2a6f
4 touches
1 conflict
0x8f45ea5c…6e99
0x34b655…2a6f
4 touches
1 conflict
0xb4656137…5858
0x34b655…2a6f
4 touches
1 conflict
0x1e9f80ea…f30d
0x34b655…2a6f
4 touches
1 conflict
0xccebf5c5…8758
0x34b655…2a6f
4 touches
1 conflict
0x84c7c379…72e8
0x34b655…2a6f
2 touches
0 conflicts
0x92b24e8a…1afa
0x34b655…2a6f
2 touches
0 conflicts
0x9cca0d37…6906
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
0x8c21151476…60b757
Audit this contract →
← previous block
·
next block →
recent activity