pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,478,850
← previous block
next block →
recent activity
Analyzing
Block #76,478,850
10 transactions · 6 stateful · 2026-05-23 12:39:05 UTC
Parallelism
80
/100
Blocked
17
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,478,850
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
swap
#2
0xab083028
#3
updateDataFeedsValuesPartial
#4
setData
#5
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
#8
execFwdPositionOps
#9
0x1b347c…5324
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9b8ae99…32b4
0x34b655…2a6f
4 touches
1 conflict
0xf9b8ae99…32b3
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x4dc004e5…21c0
0x065c9d…c394
2 touches
0 conflicts
0xbbd79e5a…b8d6
0x065c9d…c394
2 touches
0 conflicts
0xcf8c13c0…9fa9
0x065c9d…c394
2 touches
0 conflicts
0x12a9b76e…cb76
0x3bd359…433a
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:
Perpl
1 conflict on slot
0xf9b8ae99dc…3532b4
Audit this contract →
← previous block
·
next block →
recent activity