pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,573,824
← previous block
next block →
recent activity
Analyzing
Block #93,573,824
12 transactions · 9 stateful · 2026-08-06 07:28:41 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,573,824
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
execOrders
#4
0x5acec890
#5
0x5acec890
#6
execFwdPositionOps
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
0x6a743821
#10
transfer
#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
0x3a473699…6159
0x754704…b603
4 touches
1 conflict
0x8434d4d0…d5d8
0x754704…b603
4 touches
1 conflict
0x1c795b3a…8e8a
0x754704…b603
4 touches
1 conflict
0x0463db49…5d05
0x34b655…2a6f
2 touches
0 conflicts
0x09924b4d…d104
0x34b655…2a6f
2 touches
0 conflicts
0x17091c69…e7f3
0x34b655…2a6f
2 touches
0 conflicts
0x19795ad6…4a16
0x34b655…2a6f
2 touches
0 conflicts
0x19ebfd29…e80e
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:
USDC (USDC)
1 conflict on slot
0x3a4736997f…b06159
Audit this contract →
← previous block
·
next block →
recent activity