pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,401,254
← previous block
next block →
recent activity
Analyzing
Block #93,401,254
12 transactions · 11 stateful · 2026-08-05 17:01:09 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,401,254
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
updateDataFeedsValuesPartial
#4
batchUpdate
#5
execFwdPositionOps
#6
execFwdPositionOps
#7
setData
#8
execOrders
· blocks 1
#10
0x59558d29
#11
0xc7e3ec2c
#2
matchOrders
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
8
w0
9
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
0xde8a9295…0466
0x754704…b603
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x2a9e9bd1…5368
0x2a68ba…90c5
2 touches
0 conflicts
0x08148813…4912
0x34b655…2a6f
2 touches
0 conflicts
0x08d91ef5…2d7c
0x34b655…2a6f
2 touches
0 conflicts
0x04a32684…1017
0x99c7a7…8bf0
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