pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#112,369,058
← previous block
next block →
recent activity
Analyzing
Block #112,369,058
12 transactions · 7 stateful · 2026-10-11 04:07:28 UTC
Parallelism
83
/100
Blocked
14
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#112,369,058
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x59558d29
#2
0x5acec890
#3
0x928e4afa
· blocks 1
#4
execOrders
#5
execOrders
#7
redeemDelegations
#8
0x57368ddf
#9
setData
#10
0x0c7abd22
#11
0x0c7abd22
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x132e96ad…6717
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x10797f0b…439a
0x34b655…2a6f
2 touches
0 conflicts
0x12f898d0…6666
0x34b655…2a6f
2 touches
0 conflicts
0x4b5f6770…73e3
0x34b655…2a6f
2 touches
0 conflicts
0x60c02909…657d
0x34b655…2a6f
2 touches
0 conflicts
0x766f19bb…75dd
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
0x132e96ad29…196717
Audit this contract →
← previous block
·
next block →
recent activity