pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,260,674
← previous block
next block →
recent activity
Analyzing
Block #76,260,674
11 transactions · 8 stateful · 2026-05-22 12:26:24 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,260,674
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updatePrices
#3
updatePrices
#4
execPerpOps
#5
0x98717539
#6
0x98717539
· blocks 1
#8
updateDataFeedsValuesPartial
#9
setData
#10
execOrders
#7
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x908d4442…2c4b
0x34b655…2a6f
4 touches
1 conflict
0x8db1e0f2…2fcf
0x34b655…2a6f
4 touches
1 conflict
0xc6417de0…2191
0xc8689a…ee79
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1ff368bc…b881
0x065c9d…c394
2 touches
0 conflicts
0x6a7cc462…de9f
0x065c9d…c394
2 touches
0 conflicts
0xa7093cc7…f287
0x065c9d…c394
2 touches
0 conflicts
0xb0485f38…4544
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:
Perpl
1 conflict on slot
0x908d4442aa…222c4b
Audit this contract →
← previous block
·
next block →
recent activity