pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,580,157
← previous block
next block →
recent activity
Analyzing
Block #95,580,157
12 transactions · 11 stateful · 2026-08-13 08:11:30 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,580,157
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0x5acec890
#3
execOrders
#4
updateDataFeedsValuesPartial
#5
exactInputSingle
#6
execFwdPositionOps
· blocks 1
#7
0x94defb17
· blocks 1
#10
setData
#11
0x59558d29
#8
0x94defb17
#9
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w0
8
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf808bdd0…5fc1
0x968279…9342
4 touches
1 conflict
0x4a95187b…5fda
0x968279…9342
4 touches
1 conflict
0x4a95187b…5fdb
0x968279…9342
4 touches
1 conflict
0x4a95187b…5fde
0x968279…9342
4 touches
1 conflict
0x4a95187b…5fdf
0x968279…9342
4 touches
1 conflict
0x4a95187b…5fe1
0x968279…9342
4 touches
1 conflict
0xf808bdd0…5fbe
0x968279…9342
4 touches
1 conflict
0xf808bdd0…5fbf
0x968279…9342
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:
0x96827978…f09342
1 conflict on slot
0xf808bdd0b8…385fc1
Audit this contract →
← previous block
·
next block →
recent activity