pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,670,057
← previous block
next block →
recent activity
Analyzing
Block #94,670,057
11 transactions · 10 stateful · 2026-08-10 03:37:55 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,670,057
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
execOrders
· blocks 1
#4
updatePrices
#5
0x5acec890
#6
exactInputSingle
#7
execFwdPositionOps
#8
execFwdPositionOps
#9
execFwdPositionOps
#10
setData
#3
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x639eebcc…cff9
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xe4e2ed0a…a2ef
0x34b655…2a6f
3 touches
1 conflict
0x2cc85280…c2f7
0x34b655…2a6f
2 touches
0 conflicts
0x419dfa11…762c
0x34b655…2a6f
2 touches
0 conflicts
0x4f1ad4b4…e00a
0x34b655…2a6f
2 touches
0 conflicts
0x4f858307…7642
0x34b655…2a6f
2 touches
0 conflicts
0x5502e1cc…3910
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
0x639eebcc48…e2cff9
Audit this contract →
← previous block
·
next block →
recent activity