pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#112,526,086
← previous block
next block →
recent activity
Analyzing
Block #112,526,086
11 transactions · 8 stateful · 2026-10-11 17:17:31 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,526,086
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x59558d29
#2
execOrders
#3
execOrders
#4
execOrders
#5
execFwdPositionOpsV2
#6
0x84403c1b
· blocks 2
#9
0x84403c1b
#10
setData
#7
0x84403c1b
#8
0x84403c1b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c78ca04…432c
0x34b655…2a6f
4 touches
1 conflict
0x414255a9…9a81
0x34b655…2a6f
4 touches
1 conflict
0xc5d43e38…b44a
0x34b655…2a6f
4 touches
1 conflict
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
0x464a82ff…41de
0x34b655…2a6f
4 touches
1 conflict
0x3732c6c9…ded6
0x34b655…2a6f
4 touches
1 conflict
0x5cd06341…18da
0x34b655…2a6f
2 touches
0 conflicts
0x82825afa…f8bd
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
0x3c78ca0412…da432c
Audit this contract →
← previous block
·
next block →
recent activity