pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,666,844
← previous block
next block →
recent activity
Analyzing
Block #93,666,844
11 transactions · 11 stateful · 2026-08-06 15:16:19 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,666,844
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
execOrders
· blocks 1
#3
updatePrices
#5
permit2TransferAndMulticall
#7
execFwdPositionOps
#8
updateDataFeedsValuesPartial
#9
setData
#10
execOrders
#4
execOrder
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
4
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22755bc3…3056
0x34b655…2a6f
4 touches
1 conflict
0x1e56f6b6…5940
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x20492d53…80f9
0x34b655…2a6f
4 touches
1 conflict
0x0eac7709…66c3
0x34b655…2a6f
2 touches
0 conflicts
0x1e7df431…682e
0x34b655…2a6f
2 touches
0 conflicts
0x4602f03a…2dae
0x34b655…2a6f
2 touches
0 conflicts
0x4f93e8cf…8eec
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
0x22755bc3d3…013056
Audit this contract →
← previous block
·
next block →
recent activity