pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,134,685
← previous block
next block →
recent activity
Analyzing
Block #94,134,685
11 transactions · 8 stateful · 2026-08-08 06:30:03 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,134,685
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
0x5acec890
#3
execOrder
#4
execFwdPositionOps
#5
execFwdPositionOps
#6
updateDataFeedsValuesPartial
#7
placeAndExecuteMarketSell
· blocks 1
#9
0x9e76c652
#10
setData
#8
placeAndExecuteMarketSell
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa091433a…8e5d
0x065c9d…c394
4 touches
1 conflict
0x4c1fbdf6…953d
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x0778475b…bd75
0x2a68ba…90c5
4 touches
1 conflict
0x2b856d86…7988
0x34b655…2a6f
2 touches
0 conflicts
0x4392cbcd…6a92
0x34b655…2a6f
2 touches
0 conflicts
0x4d314322…c58c
0x34b655…2a6f
2 touches
0 conflicts
0x4f4bdabd…ffba
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-MON/USDC
1 conflict on slot
0xa091433abf…578e5d
Audit this contract →
← previous block
·
next block →
recent activity