pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,750,752
← previous block
next block →
recent activity
Analyzing
Block #93,750,752
11 transactions · 9 stateful · 2026-08-06 22:18:09 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,750,752
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
execOrders
#4
updateDataFeedsValuesPartial
#5
0x5acec890
· blocks 1
#6
execFwdPositionOps
#8
placeAndExecuteMarketBuy
#9
setData
#10
execOrders
#3
execOrders
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfed09e59…a493
0x34b655…2a6f
4 touches
1 conflict
0x0bc506f8…92a2
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x033cf007…136d
0x34b655…2a6f
2 touches
0 conflicts
0x03aa8b26…118a
0x34b655…2a6f
2 touches
0 conflicts
0x0bee8017…c90a
0x34b655…2a6f
2 touches
0 conflicts
0x23ce455e…41ae
0x34b655…2a6f
2 touches
0 conflicts
0x3782a203…e472
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
0xfed09e59c7…d6a493
Audit this contract →
← previous block
·
next block →
recent activity