pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,117,158
← previous block
next block →
recent activity
Analyzing
Block #76,117,158
12 transactions · 12 stateful · 2026-05-21 20:30:41 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,117,158
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute
#2
exactInputSingle
#3
0xab083028
· blocks 2
#4
updatePrices
#5
0x678292e2
#6
0x98717539
#8
0xaf47a8bb
· blocks 1
#11
setData
#7
0xed82b078
· blocks 1
#9
0xaf47a8bb
#10
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
8
w0
9
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x41755291…977f
0x065c9d…c394
6 touches
3 conflicts
0x67d846dd…358c
0x6661d3…7777
4 touches
1 conflict
0x9527c4ff…73fb
0x6661d3…7777
4 touches
1 conflict
0x631ab234…2d48
0x9f3832…4ae4
4 touches
1 conflict
0x631ab234…2d49
0x9f3832…4ae4
4 touches
1 conflict
0x7cf5136f…ba69
0x9f3832…4ae4
4 touches
1 conflict
0xd2d29721…e0fb
0x9f3832…4ae4
4 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:
Kuru Exchange: Market-MON/USDC
3 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity