pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,566,920
← previous block
next block →
recent activity
Analyzing
Block #93,566,920
11 transactions · 10 stateful · 2026-08-06 06:53:59 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,566,920
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execute_route
#3
updateDataFeedsValuesPartial
#4
0x928e4afa
· blocks 1
#5
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
#8
placeAndExecuteMarketSell
#9
setData
#7
execFwdPositionOps
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w0
7
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb657a90…637f
0x34b655…2a6f
4 touches
1 conflict
0x503c09b7…9442
0x34b655…2a6f
4 touches
1 conflict
0x66200811…5433
0x34b655…2a6f
4 touches
1 conflict
0x750fb05c…0e99
0x34b655…2a6f
4 touches
1 conflict
0x7a606d8a…9700
0x34b655…2a6f
4 touches
1 conflict
0xb5a3b1be…8122
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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:
Perpl
1 conflict on slot
0xfb657a904b…f4637f
Audit this contract →
← previous block
·
next block →
recent activity