pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,277,139
← previous block
next block →
recent activity
Analyzing
Block #95,277,139
10 transactions · 7 stateful · 2026-08-12 06:42:41 UTC
Parallelism
70
/100
Blocked
29
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,277,139
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
· blocks 1
#2
placeAndExecuteMarketBuy
#3
placeAndExecuteMarketBuy
#5
forward
#7
updateDataFeedsValuesPartial
#8
0x6a7c1659
#9
setData
#4
execFwdPositionOps
· blocks 1
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5419303…8d89
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x08636046…e60f
0x34b655…2a6f
4 touches
1 conflict
0x013ae495…0573
0x34b655…2a6f
2 touches
0 conflicts
0x02099df4…08d2
0x34b655…2a6f
2 touches
0 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
2 touches
0 conflicts
0x1321736a…43e3
0x34b655…2a6f
2 touches
0 conflicts
0x17c3727d…cb0e
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
0xa541930306…eb8d89
Audit this contract →
← previous block
·
next block →
recent activity