pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,141,848
← previous block
next block →
recent activity
Analyzing
Block #76,141,848
10 transactions · 10 stateful · 2026-05-21 23:15:04 UTC
Parallelism
60
/100
Blocked
30
%
Avg conflicts / tx
0.4
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,141,848
· 10 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#4
forward
#6
updateDataFeedsValuesPartial
#7
0xe9316489
#8
setData
#9
0x39435dac
#2
0x0c7abd22
· blocks 2
#3
0xccf50a51
· blocks 1
#5
modifyLiquidities
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
5
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0xddcd39ea…62ef
0x065c9d…c394
4 touches
1 conflict
0x4979282b…2936
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x92d610a6…9a40
0x2a68ba…90c5
4 touches
1 conflict
0xdb78557b…56e3
0xd32edf…ff58
3 touches
1 conflict
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
0x17606ba612…ea1b6e
Audit this contract →
← previous block
·
next block →
recent activity