pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,550,626
← previous block
next block →
recent activity
Analyzing
Block #93,550,626
12 transactions · 10 stateful · 2026-08-06 05:32:04 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,550,626
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a741ccc
#2
execPerpOps
#3
execPerpOps
#4
execFwdPositionOps
#5
placeAndExecuteMarketBuy
#6
0x3f5c179b
#7
forward
#8
0xe9316489
· blocks 1
#10
setData
#11
execOrders
#9
0xe9316489
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38176ba5…f975
0x96b79e…d00a
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x1e10796e…6213
0x34b655…2a6f
2 touches
0 conflicts
0x1e10796e…6214
0x34b655…2a6f
2 touches
0 conflicts
0x3f39444c…0b9e
0x34b655…2a6f
2 touches
0 conflicts
0x47ee9f76…8dee
0x34b655…2a6f
2 touches
0 conflicts
0x47ee9f76…8def
0x34b655…2a6f
2 touches
0 conflicts
0x6a472afb…bc23
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:
0x96b79ef4…d2d00a
1 conflict on slot
0x38176ba5b7…39f975
Audit this contract →
← previous block
·
next block →
recent activity