pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#112,246,666
← previous block
next block →
recent activity
Analyzing
Block #112,246,666
11 transactions · 8 stateful · 2026-10-10 17:51:41 UTC
Parallelism
82
/100
Blocked
25
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#112,246,666
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x9ac0761c
· blocks 1
#3
0x59558d29
#4
0x928e4afa
#5
execPerpOps
· blocks 1
#7
execFwdPositionOpsV2
#8
setData
#9
execOrders
#10
0x0c7abd22
#2
0x9ac0761c
#6
execPerpOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a4f488f…d8ec
0xf42df8…ad97
4 touches
1 conflict
0xfdd40e24…dca0
0x34b655…2a6f
4 touches
1 conflict
0x7954ece9…fef0
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0xbce62604…ff5c
0x34b655…2a6f
4 touches
1 conflict
0xbd3b7133…f360
0x34b655…2a6f
4 touches
1 conflict
0xccebf5c5…8758
0x34b655…2a6f
4 touches
1 conflict
0x4dc8c6f0…dd57
0x34b655…2a6f
3 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:
0xf42df81a…61ad97
1 conflict on slot
0x2a4f488f97…7ed8ec
Audit this contract →
← previous block
·
next block →
recent activity