pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,557,921
← previous block
next block →
recent activity
Analyzing
Block #93,557,921
9 transactions · 8 stateful · 2026-08-06 06:08:45 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,557,921
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
artefact_keep
#4
execFwdPositionOps
#5
execFwdPositionOps
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
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
0x1c795b3a…8e8a
0x754704…b603
4 touches
1 conflict
0x3a473699…6159
0x754704…b603
4 touches
1 conflict
0x8434d4d0…d5d8
0x754704…b603
4 touches
1 conflict
0xa9fde395…e204
0x99c7a7…8bf0
4 touches
1 conflict
0xb3faae62…90d9
0x99c7a7…8bf0
4 touches
1 conflict
0x0dd3d3cd…7281
0x34b655…2a6f
2 touches
0 conflicts
0x15be757a…275e
0x34b655…2a6f
2 touches
0 conflicts
0x15be757a…275f
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
0x1c795b3af4…ff8e8a
Audit this contract →
← previous block
·
next block →
recent activity