pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,540,121
← previous block
next block →
recent activity
Analyzing
Block #93,540,121
10 transactions · 9 stateful · 2026-08-06 04:39:16 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,540,121
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
execOrders
#3
0x5acec890
· blocks 1
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
· blocks 1
#7
updateDataFeedsValuesPartial
#8
setData
#6
execFwdPositionOps
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w0
5
w0
6
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb392027…0308
0x34b655…2a6f
4 touches
1 conflict
0xf04b3287…fd51
0x34b655…2a6f
4 touches
1 conflict
0xf726e2e2…e561
0x34b655…2a6f
4 touches
1 conflict
0x1730ab3c…ce37
0x34b655…2a6f
4 touches
1 conflict
0x17c3727d…cb0e
0x34b655…2a6f
4 touches
1 conflict
0x1b49f420…7fe1
0x34b655…2a6f
4 touches
1 conflict
0x4cb89fd4…9bb8
0x34b655…2a6f
4 touches
1 conflict
0x53b5920b…58f8
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
0xdb39202701…2d0308
Audit this contract →
← previous block
·
next block →
recent activity