pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,467,406
← previous block
next block →
recent activity
Analyzing
Block #93,467,406
12 transactions · 10 stateful · 2026-08-05 22:33:44 UTC
Parallelism
83
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,467,406
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
execOrders
#3
execFwdPositionOps
· blocks 1
#5
0xb2d4797b
#6
updateDataFeedsValuesPartial
#7
0x6a73babf
#8
transfer
· blocks 1
#10
setData
#11
0xc7e3ec2c
#4
execFwdPositionOps
#9
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x91b0f8ed…6bd6
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0x11db128b…1153
0x34b655…2a6f
2 touches
0 conflicts
0x50cd5802…d011
0x34b655…2a6f
2 touches
0 conflicts
0x58620f29…db5a
0x34b655…2a6f
2 touches
0 conflicts
0x76836137…d765
0x34b655…2a6f
2 touches
0 conflicts
0x861e5aef…d32c
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
0x42041feca2…afbd86
Audit this contract →
← previous block
·
next block →
recent activity