pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,674,781
← previous block
next block →
recent activity
Analyzing
Block #94,674,781
8 transactions · 6 stateful · 2026-08-10 04:01:40 UTC
Parallelism
50
/100
Blocked
50
%
Avg conflicts / tx
0.75
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,674,781
· 8 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
execOrders
· blocks 3
#3
execOrders
#4
exactInputSingle
#7
setData
#2
execOrders
· blocks 2
#5
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w2
6
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x40bc5adc…eda6
0x34b655…2a6f
6 touches
3 conflicts
0x4188cc5f…2d2e
0x34b655…2a6f
4 touches
1 conflict
0x0fa3a390…25da
0x34b655…2a6f
2 touches
0 conflicts
0x1d0a04dd…b892
0x34b655…2a6f
2 touches
0 conflicts
0x24b08f9c…e594
0x34b655…2a6f
2 touches
0 conflicts
0x27a78688…b891
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
6 conflicts on slot
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity