pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,278,141
← previous block
next block →
recent activity
Analyzing
Block #95,278,141
11 transactions · 11 stateful · 2026-08-12 06:47:44 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,278,141
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
executeBatch
#2
execFwdPositionOps
#3
0xed82b078
#4
execFwdPositionOps
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x59558d29
#9
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x82dd2252…e1ce
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x09e0690d…6e3d
0xe52b14…7230
2 touches
0 conflicts
0x0b0c2e8d…c1b8
0xe52b14…7230
2 touches
0 conflicts
0x17bbe4f8…08c5
0xe52b14…7230
2 touches
0 conflicts
0x28747f91…a9fd
0xe52b14…7230
2 touches
0 conflicts
0x3cebc8f1…975c
0xe52b14…7230
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
0x82dd22520c…26e1ce
Audit this contract →
← previous block
·
next block →
recent activity