pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#112,350,473
← previous block
next block →
recent activity
Analyzing
Block #112,350,473
11 transactions · 11 stateful · 2026-10-11 02:33:57 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.27
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#112,350,473
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x59558d29
#3
0x5acec890
#4
execFwdPositionOpsV2
#5
0x84403c1b
· blocks 1
#6
0x84403c1b
· blocks 2
#8
forward
#9
setData
#7
0x84403c1b
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w0
7
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x12a47c18…fc4e
0x34b655…2a6f
4 touches
1 conflict
0x38befc08…20c8
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x812d3a32…10fe
0x34b655…2a6f
4 touches
1 conflict
0x948df775…931a
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc4550172…3d03
0x34b655…2a6f
4 touches
1 conflict
0xccebf5c5…8758
0x34b655…2a6f
4 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:
Perpl
1 conflict on slot
0x12a47c18e4…eafc4e
Audit this contract →
← previous block
·
next block →
recent activity