pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,112,109
← previous block
next block →
recent activity
Analyzing
Block #95,112,109
12 transactions · 12 stateful · 2026-08-11 16:43:44 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,112,109
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
0x785f5745
#5
execFwdPositionOps
· blocks 1
#7
0x94defb17
· blocks 1
#9
commit
#10
transfer
#11
setData
#6
execFwdPositionOps
#8
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w0
6
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x47e2ecd7…3d7b
0x968279…9342
4 touches
1 conflict
0x47e2ecd7…3d79
0x968279…9342
4 touches
1 conflict
0x47e2ecd7…3d7a
0x968279…9342
4 touches
1 conflict
0x31b39922…1e65
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
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
0x47e2ecd78c…113d7b
Audit this contract →
← previous block
·
next block →
recent activity