pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,448,386
← previous block
next block →
recent activity
Analyzing
Block #76,448,386
13 transactions · 10 stateful · 2026-05-23 09:16:14 UTC
Parallelism
77
/100
Blocked
30
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,448,386
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute
#2
exactInputSingle
#3
0xab083028
· blocks 3
#6
0x98717539
#7
aggregate3
#8
updateDataFeedsValuesPartial
#10
0xc5a04723
#11
setData
#12
0x36326531
#4
batchUpdate
· blocks 1
#5
batchUpdate
· blocks 1
#9
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc8faac2…c766
0x065c9d…c394
6 touches
3 conflicts
0x18cf3003…51d1
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6ebd6a9d…be16
0x065c9d…c394
4 touches
1 conflict
0x73a76f2d…3959
0x065c9d…c394
3 touches
1 conflict
0x77c441cc…ba48
0x065c9d…c394
3 touches
1 conflict
0x4dd1db39…a995
0x188d58…ea8e
2 touches
0 conflicts
0x06e40499…165e
0x1d1325…2305
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-MON/USDC
3 conflicts on slot
0xcc8faac238…88c766
Audit this contract →
← previous block
·
next block →
recent activity