pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,782,920
← previous block
next block →
recent activity
Analyzing
Block #90,782,920
11 transactions · 10 stateful · 2026-07-27 13:24:49 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,782,920
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
executeAndRescue
#2
exactInputSingle
#3
execFwdPositionOps
· blocks 1
#4
executeBatch
#6
batchUpdate
#7
execOrders
#8
setData
#9
0x59558d29
· blocks 1
#5
execFwdPositionOps
#10
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2e52e46…0894
0x34b655…2a6f
4 touches
1 conflict
0x0ad1fc8b…7516
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x92339d95…0801
0x0000a8…8888
2 touches
0 conflicts
0x2f0c7a17…9360
0x34b655…2a6f
2 touches
0 conflicts
0x2f0c7a17…9361
0x34b655…2a6f
2 touches
0 conflicts
0x32a7576e…21b6
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
0xe2e52e4663…6f0894
Audit this contract →
← previous block
·
next block →
recent activity