pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,505,719
← previous block
next block →
recent activity
Analyzing
Block #93,505,719
12 transactions · 10 stateful · 2026-08-06 01:46:20 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,505,719
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
0xab083028
#4
0x0c7abd22
#5
execOrders
#6
0x41a8f47c
#7
0x5acec890
#8
verifyOracleProofV2
#9
execFwdPositionOps
#10
execFwdPositionOps
#11
setData
#2
matchOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x29ba534c…fe06
0x754704…b603
4 touches
1 conflict
0x303ace4f…eae8
0x754704…b603
4 touches
1 conflict
0x8454e259…1300
0x99c7a7…8bf0
4 touches
1 conflict
0xed697895…3bf6
0x99c7a7…8bf0
4 touches
1 conflict
0x0e854949…baa7
0x754704…b603
4 touches
1 conflict
0x099dab8e…37fc
0x8f415d…5241
3 touches
1 conflict
0xfad485ae…8a51
0x065c9d…c394
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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:
USDC (USDC)
1 conflict on slot
0x29ba534cc1…7efe06
Audit this contract →
← previous block
·
next block →
recent activity