pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,113,850
← previous block
next block →
recent activity
Analyzing
Block #76,113,850
11 transactions · 9 stateful · 2026-05-21 20:08:39 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,113,850
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
· blocks 1
#2
0xed82b078
#4
0x0c7abd22
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#8
redeemDelegations
#9
execOrders
· blocks 1
#3
0xab083028
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x15dfc675…c5e2
0xa6afd3…d132
4 touches
1 conflict
0x1b159f3d…9163
0x34b655…2a6f
4 touches
1 conflict
0xae5e65b8…4311
0xa6afd3…d132
3 touches
1 conflict
0xb46f2e8c…8b7e
0xa6afd3…d132
3 touches
1 conflict
0x10abefc9…c9bc
0x1d1325…2305
2 touches
0 conflicts
0x10d80fee…dbda
0x1d1325…2305
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity