pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,194,957
← previous block
next block →
recent activity
Analyzing
Block #76,194,957
16 transactions · 14 stateful · 2026-05-22 05:08:44 UTC
Parallelism
88
/100
Blocked
7
%
Avg conflicts / tx
0.06
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,194,957
· 16 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
removeLiquidity
#3
updatePrices
#4
0x0c7abd22
#5
0xccf50a51
#6
0x98717539
#7
0xed82b078
#8
0x62be7533
#9
redeemDelegations
#10
0x45761772
· blocks 1
#12
executeBatch
#13
collect
#14
updateDataFeedsValuesPartial
#15
setData
#11
0x45761772
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…000d
0x46a15b…4364
4 touches
1 conflict
0x405787fa…ee8a
0x46a15b…4364
4 touches
1 conflict
0x5ad5d7b5…6f91
0x46a15b…4364
3 touches
1 conflict
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0x33018431…8f5c
0x188d58…ea8e
2 touches
0 conflicts
0x33018431…8f5e
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0004
0x5afd3e…7620
2 touches
0 conflicts
0x3b848bb1…0150
0x5afd3e…7620
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:
0x46a15b0b…7f4364
1 conflict on slot
0x0000000000…00000d
Audit this contract →
← previous block
·
next block →
recent activity