pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,398,681
← previous block
next block →
recent activity
Analyzing
Block #93,398,681
12 transactions · 9 stateful · 2026-08-05 16:48:13 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,398,681
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
matchOrders
· blocks 1
#4
0x6a7369c5
#5
execFwdPositionOps
#6
execFwdPositionOps
#7
updateDataFeedsValuesPartial
#8
0x3f5c179b
#9
batchCancelOrders
#10
setData
#11
0x59558d29
#3
matchOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17530abf…5f20
0x754704…b603
4 touches
1 conflict
0x9feedc78…da4a
0x754704…b603
4 touches
1 conflict
0xfe4e584c…50ff
0x754704…b603
4 touches
1 conflict
0x0a280e29…8617
0x99c7a7…8bf0
4 touches
1 conflict
0xf97ccefb…468f
0x99c7a7…8bf0
4 touches
1 conflict
0x04e17b28…d9f0
0x34b655…2a6f
2 touches
0 conflicts
0x08636046…e60f
0x34b655…2a6f
2 touches
0 conflicts
0x0efc210e…70ab
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
0x17530abfa8…b85f20
Audit this contract →
← previous block
·
next block →
recent activity