pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,590,052
← previous block
next block →
recent activity
Analyzing
Block #95,590,052
11 transactions · 9 stateful · 2026-08-13 09:01:16 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,590,052
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0xab083028
#3
execOrder
· blocks 1
#4
updatePrices
#5
0x5acec890
#6
updateDataFeedsValuesPartial
#8
0xb2d4797b
#9
0x6a7d8854
#10
setData
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c47eb8c…d3a4
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x08e8f2c9…a11a
0x34b655…2a6f
2 touches
0 conflicts
0x253e6614…8ce5
0x34b655…2a6f
2 touches
0 conflicts
0x5e8ddd73…4dfb
0x34b655…2a6f
2 touches
0 conflicts
0x8eb21bd9…aa8b
0x34b655…2a6f
2 touches
0 conflicts
0x948836ff…59ab
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
0x5c47eb8c77…41d3a4
Audit this contract →
← previous block
·
next block →
recent activity