pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,261,649
← previous block
next block →
recent activity
Analyzing
Block #76,261,649
10 transactions · 8 stateful · 2026-05-22 12:32:54 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,261,649
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updatePrices
#3
execFwdPositionOps
#4
updateDataFeedsValuesPartial
#5
0xed82b078
#6
execFwdPositionOps
#7
setData
#8
execOrders
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x764256b9…91a5
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x3347cbe5…846c
0x34b655…2a6f
4 touches
1 conflict
0x65e795ca…0320
0x34b655…2a6f
4 touches
1 conflict
0x515b3963…4331
0x065c9d…c394
2 touches
0 conflicts
0x7b34f03c…5c8a
0x065c9d…c394
2 touches
0 conflicts
0xcfa326b0…6f2c
0x065c9d…c394
2 touches
0 conflicts
0xe0e444de…96b6
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
0x764256b9c7…5d91a5
Audit this contract →
← previous block
·
next block →
recent activity