pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,576,594
← previous block
next block →
recent activity
Analyzing
Block #93,576,594
12 transactions · 11 stateful · 2026-08-06 07:42:37 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,576,594
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
#6
0x3f5c179b
· blocks 1
#7
forward
#9
execFwdPositionOps
#10
setData
#11
execOrders
#8
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x890a1db9…1712
0xa6afd3…d132
4 touches
1 conflict
0x0419260c…d009
0x34b655…2a6f
2 touches
0 conflicts
0x0494220d…abf7
0x34b655…2a6f
2 touches
0 conflicts
0x0a005879…de60
0x34b655…2a6f
2 touches
0 conflicts
0x0ae9d2df…f787
0x34b655…2a6f
2 touches
0 conflicts
0x0ae9d2df…f788
0x34b655…2a6f
2 touches
0 conflicts
0x0eef9302…e59b
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:
Kuru Exchange: Market-WETH/USDC
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity