pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,507,456
← previous block
next block →
recent activity
Analyzing
Block #76,507,456
11 transactions · 7 stateful · 2026-05-23 15:49:35 UTC
Parallelism
82
/100
Blocked
29
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,507,456
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#4
0x05ee6a22
#5
0x05ee6a22
#6
updateDataFeedsValuesPartial
#7
updatePriceFeedsIfNecessary
#8
forward
#9
forward
#10
setData
#2
0x1094dc9f
#3
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e24eaaa…1508
0xa6afd3…d132
3 touches
1 conflict
0x7df5d157…a40c
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001d
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002d
0x1b6862…e19c
2 touches
0 conflicts
0xba5743c7…21c4
0x1b6862…e19c
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:
Kuru Exchange: Market-WETH/USDC
1 conflict on slot
0x8e24eaaa8e…e61508
Audit this contract →
← previous block
·
next block →
recent activity