pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,090,122
← previous block
next block →
recent activity
Analyzing
Block #76,090,122
15 transactions · 9 stateful · 2026-05-21 17:30:33 UTC
Parallelism
87
/100
Blocked
33
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,090,122
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x719d975a
· blocks 1
#2
updatePrices
· blocks 1
#4
updatePrices
#5
updatePrices
#6
updatePrices
#7
updatePrices
#8
0xed82b078
· blocks 1
#10
updateDataFeedsValuesPartial
#12
0x0c7abd22
#13
forward
#14
setData
#3
updatePrices
#9
0x62be7533
#11
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
8
w0
9
w1
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x696a27c8…5847
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0e4ddae9…eeab
0x065c9d…c394
4 touches
1 conflict
0x2bb64fb7…ec2e
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x11b69a7e…334e
0xee8c0e…1242
4 touches
1 conflict
0x00000000…0000
0xc11090…fd82
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: MarginAccount
1 conflict on slot
0x696a27c88b…5a5847
Audit this contract →
← previous block
·
next block →
recent activity