pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#77,516,281
← previous block
next block →
recent activity
Analyzing
Block #77,516,281
10 transactions · 8 stateful · 2026-05-28 07:50:43 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#77,516,281
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
_makeSwaps
· blocks 2
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
execute
#6
setData
#7
0x6a17f44b
#9
execOrders
#5
0x62be7533
· blocks 1
#8
execute
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xad5aa25c…1772
0x065c9d…c394
4 touches
1 conflict
0x62e20208…be65
0x0555e3…2b9c
2 touches
0 conflicts
0xee0a9ebb…c425
0x0555e3…2b9c
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x094452…0a09
2 touches
0 conflicts
0x00000000…0003
0x094452…0a09
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)
3 conflicts on slot
0xa1087a5ca6…0a66c4
Audit this contract →
← previous block
·
next block →
recent activity