pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,467,737
← previous block
next block →
recent activity
Analyzing
Block #93,467,737
11 transactions · 9 stateful · 2026-08-05 22:35:24 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,467,737
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0xab083028
#3
execPerpOps
#4
execPerpOps
#5
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
#7
execOrders
#9
0x6a73bb23
#10
setData
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb443d4db…2a77
0x34b655…2a6f
4 touches
1 conflict
0xfb8f62bc…947e
0x34b655…2a6f
4 touches
1 conflict
0x21b7fccc…7d9a
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x9c092d51…c906
0x34b655…2a6f
4 touches
1 conflict
0x9c092d51…c907
0x34b655…2a6f
4 touches
1 conflict
0xd676e291…3ecf
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
0xb443d4db64…cb2a77
Audit this contract →
← previous block
·
next block →
recent activity