pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,277,559
← previous block
next block →
recent activity
Analyzing
Block #95,277,559
12 transactions · 9 stateful · 2026-08-12 06:44:48 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,277,559
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exactInputSingle
#2
execFwdPositionOps
#3
execFwdPositionOps
· blocks 1
#4
updateDataFeedsValuesPartial
#5
execOrders
· blocks 1
#7
0x6a7c16d8
#8
setData
#9
0x59558d29
#10
execOrders
#11
execOrders
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x0672e4a2…8d1f
0x34b655…2a6f
2 touches
0 conflicts
0x0712100b…e8bc
0x34b655…2a6f
2 touches
0 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
2 touches
0 conflicts
0x1122b86f…e4c8
0x34b655…2a6f
2 touches
0 conflicts
0x1b49f420…7fe1
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
0xbde524f475…b143bf
Audit this contract →
← previous block
·
next block →
recent activity