pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,854,340
← previous block
next block →
recent activity
Analyzing
Block #93,854,340
11 transactions · 8 stateful · 2026-08-07 06:58:55 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,854,340
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
multicall
#3
execOrders
#4
0x5acec890
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
execFwdPositionOps
· blocks 1
#8
execFwdPositionOps
· blocks 1
#10
setData
#9
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a3d2527…8ca0
0x34b655…2a6f
4 touches
1 conflict
0x4102cb2a…3b17
0x34b655…2a6f
4 touches
1 conflict
0x000bde1a…e123
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd6ee97ff…2074
0x34b655…2a6f
4 touches
1 conflict
0x1321736a…43e3
0x34b655…2a6f
2 touches
0 conflicts
0xa3c36de0…3cf3
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
0x1a3d2527fb…8a8ca0
Audit this contract →
← previous block
·
next block →
recent activity