pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,501,348
← previous block
next block →
recent activity
Analyzing
Block #93,501,348
13 transactions · 12 stateful · 2026-08-06 01:24:22 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,501,348
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0xa96df62f
#3
execOrders
· blocks 1
#4
execPerpOps
#5
execPerpOps
#6
update
#7
executeMessage
#8
updateDataFeedsValuesPartial
#9
execFwdPositionOps
· blocks 1
#10
0x3f5c179b
#11
setData
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
9
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52b477bc…7ccf
0x34b655…2a6f
4 touches
1 conflict
0x55ce57a3…f7d1
0x34b655…2a6f
4 touches
1 conflict
0xa13e2069…6171
0x34b655…2a6f
4 touches
1 conflict
0xb1b58b33…874f
0x34b655…2a6f
4 touches
1 conflict
0x08330b36…ae29
0x34b655…2a6f
4 touches
1 conflict
0x30c0f89e…b0db
0x34b655…2a6f
2 touches
0 conflicts
0x3f39444c…0b9e
0x34b655…2a6f
2 touches
0 conflicts
0x49753bca…432e
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
0x52b477bcb8…5d7ccf
Audit this contract →
← previous block
·
next block →
recent activity