pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#112,246,637
← previous block
next block →
recent activity
Analyzing
Block #112,246,637
10 transactions · 8 stateful · 2026-10-10 17:51:33 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#112,246,637
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x32d01e04
#2
0x59558d29
#3
0x5acec890
#4
updatePrices
#5
execFwdPositionOpsV2
#6
0x84403c1b
· blocks 1
#8
0x84403c1b
#9
setData
#7
0x84403c1b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x28c180e1…f1e2
0x34b655…2a6f
4 touches
1 conflict
0xb66366c3…fc81
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x1fb37a…a010
2 touches
0 conflicts
0x09182ada…e57f
0x34b655…2a6f
2 touches
0 conflicts
0x2081626e…9e3a
0x34b655…2a6f
2 touches
0 conflicts
0x2ce9949b…234a
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
0xea02471df2…601542
Audit this contract →
← previous block
·
next block →
recent activity