pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#112,611,875
← previous block
next block →
recent activity
Analyzing
Block #112,611,875
11 transactions · 10 stateful · 2026-10-12 00:29:09 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#112,611,875
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x4297b034
#4
updatePrices
· blocks 1
#5
updatePrices
#7
updatePrices
#8
updateDataFeedsValuesPartial
#9
execFwdPositionOpsV2
#10
execOrders
#2
0x0c7abd22
#6
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x622d16e8…65b4
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xd381d0e5…7438
0x1b6862…e19c
4 touches
1 conflict
0x84606940…bbeb
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0002
0x125f12…a50b
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 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:
ShMonad (shMON)
1 conflict on slot
0x622d16e8ff…4565b4
Audit this contract →
← previous block
·
next block →
recent activity