pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#112,371,960
← previous block
next block →
recent activity
Analyzing
Block #112,371,960
8 transactions · 7 stateful · 2026-10-11 04:22:04 UTC
Parallelism
63
/100
Blocked
29
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#112,371,960
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x59558d29
#2
0x5acec890
#3
0x928e4afa
· blocks 1
#6
0x57368ddf
#7
setData
#4
execFwdPositionOpsV2
· blocks 1
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x132e96ad…6717
0x34b655…2a6f
4 touches
1 conflict
0x10797f0b…439a
0x34b655…2a6f
2 touches
0 conflicts
0x10ffbe67…41c1
0x34b655…2a6f
2 touches
0 conflicts
0x3b3f053b…d6e1
0x34b655…2a6f
2 touches
0 conflicts
0x4401c2f3…5395
0x34b655…2a6f
2 touches
0 conflicts
0x4b227bc5…d19d
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity