pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,538,758
← previous block
next block →
recent activity
Analyzing
Block #93,538,758
11 transactions · 11 stateful · 2026-08-06 04:32:25 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,538,758
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
execFwdPositionOps
#3
execFwdPositionOps
· blocks 1
#4
executeBatch
#5
placeAndExecuteMarketBuy
#6
0x3f5c179b
#8
execFwdPositionOps
#9
0x6a740ed1
#10
setData
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x1e2721…7805
2 touches
0 conflicts
0x0e0c66fe…796f
0x1e2721…7805
2 touches
0 conflicts
0x0fb9e50c…1a35
0x34b655…2a6f
2 touches
0 conflicts
0x0fd87a64…6651
0x34b655…2a6f
2 touches
0 conflicts
0x157536c0…33ef
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
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity