pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#112,213,918
← previous block
next block →
recent activity
Analyzing
Block #112,213,918
10 transactions · 9 stateful · 2026-10-10 15:06:56 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#112,213,918
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
0x59558d29
#3
0xab083028
#4
0x5acec890
· blocks 1
#5
0x5acec890
#8
0x8b80a919
#9
setData
#6
0x0c7abd22
· blocks 1
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4de0b2a2…784f
0xc8689a…ee79
4 touches
1 conflict
0x66abbc52…98c0
0x34b655…2a6f
4 touches
1 conflict
0xb84d235f…21be
0x34b655…2a6f
4 touches
1 conflict
0xc0d73aee…d36d
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xf324b405…ca30
0x34b655…2a6f
4 touches
1 conflict
0x235b6aa7…ec37
0x37db7f…ec7b
4 touches
1 conflict
0x47c4f650…509c
0x37db7f…ec7b
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: Settlement / Helper
1 conflict on slot
0x4de0b2a2dc…5e784f
Audit this contract →
← previous block
·
next block →
recent activity