pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,563,493
← previous block
next block →
recent activity
Analyzing
Block #93,563,493
10 transactions · 9 stateful · 2026-08-06 06:36:45 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,563,493
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#5
placeAndExecuteMarketBuy
#7
0x6a742bf5
#8
transfer
#9
setData
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a5cd535…3546
0x34b655…2a6f
4 touches
1 conflict
0x20bfdd90…60df
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1473e67a…8ea0
0x34b655…2a6f
2 touches
0 conflicts
0x15336fe3…1f37
0x34b655…2a6f
2 touches
0 conflicts
0x46c8e565…d7a8
0x34b655…2a6f
2 touches
0 conflicts
0x0e854949…baa7
0x754704…b603
2 touches
0 conflicts
0x303ace4f…eae8
0x754704…b603
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
0x3a5cd53588…273546
Audit this contract →
← previous block
·
next block →
recent activity