pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,110,811
← previous block
next block →
recent activity
Analyzing
Block #76,110,811
15 transactions · 9 stateful · 2026-05-21 19:48:22 UTC
Parallelism
87
/100
Blocked
11
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,110,811
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5339c59f
· blocks 1
#2
updatePrices
#3
updatePrices
#4
updatePrices
#5
updatePrices
#6
0x98717539
#7
approve
#8
0xed82b078
· blocks 1
#9
updateDataFeedsValuesPartial
#11
forward
#12
0x2f9b08…8038
#13
0xa6afbd…ea8f
#14
setData
#10
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
8
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x47b807a2…3307
0x065c9d…c394
2 touches
0 conflicts
0x534ddabb…49b3
0x065c9d…c394
2 touches
0 conflicts
0x5508a0d8…986b
0x065c9d…c394
2 touches
0 conflicts
0x84ce69d6…ffaa
0x065c9d…c394
2 touches
0 conflicts
0xe21bf4db…479d
0x065c9d…c394
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
1 conflict on slot
0x4175529119…79977f
Audit this contract →
← previous block
·
next block →
recent activity