pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#112,612,305
← previous block
next block →
recent activity
Analyzing
Block #112,612,305
9 transactions · 9 stateful · 2026-10-12 00:31:19 UTC
Parallelism
78
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#112,612,305
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x59558d29
#2
0x928e4afa
· blocks 1
#3
execPerpOps
· blocks 1
#6
execFwdPositionOpsV2
#7
0xf146579f
#8
setData
#4
execPerpOps
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa907059a…6dc4
0x34b655…2a6f
4 touches
1 conflict
0x77762137…2893
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x077d58c3…8ed7
0x34b655…2a6f
2 touches
0 conflicts
0x68c07cb9…ae14
0x34b655…2a6f
2 touches
0 conflicts
0x85ea233a…e9c0
0x34b655…2a6f
2 touches
0 conflicts
0x8b76e9f2…54ee
0x34b655…2a6f
2 touches
0 conflicts
0x9ae859db…2d84
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
0xa907059a1d…096dc4
Audit this contract →
← previous block
·
next block →
recent activity