pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,750,713
← previous block
next block →
recent activity
Analyzing
Block #94,750,713
10 transactions · 10 stateful · 2026-08-10 10:24:47 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,750,713
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
· blocks 1
#3
0x5acec890
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
#7
0x6a79a767
#8
setData
#9
0xc7e3ec2c
#2
0x5acec890
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7a1531cd…7319
0x34b655…2a6f
4 touches
1 conflict
0x8f203394…f2db
0x34b655…2a6f
4 touches
1 conflict
0x8f203394…f2dc
0x34b655…2a6f
4 touches
1 conflict
0x4947e67f…aa39
0x34b655…2a6f
4 touches
1 conflict
0xa39840e9…088d
0x34b655…2a6f
4 touches
1 conflict
0xb138d087…4689
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…153c
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…154a
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
0x7a1531cd66…867319
Audit this contract →
← previous block
·
next block →
recent activity