pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,111,361
← previous block
next block →
recent activity
Analyzing
Block #76,111,361
12 transactions · 11 stateful · 2026-05-21 19:52:01 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,111,361
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute302
· blocks 1
#3
updatePrices
#4
redeemDelegations
#5
updateDataFeedsValuesPartial
#6
executeBatch
#7
0x0c7abd22
#8
forward
#9
updateDataFeedsValuesPartial
#10
setData
#11
redeemDelegations
#2
execute302
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52c63247…ce02
0x0a3323…0a3c
4 touches
1 conflict
0x446f2734…8b54
0x0a3323…0a3c
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x6a20fb…9b5a
2 touches
0 conflicts
0xff3addfc…633e
0x6f4756…dd5b
2 touches
0 conflicts
0x5149ba0e…d954
0x754704…b603
2 touches
0 conflicts
0xd58b5c38…3b7c
0x754704…b603
2 touches
0 conflicts
0x00000000…0002
0xab3526…fa38
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:
0x0a332311…6e0a3c
1 conflict on slot
0x52c63247e1…bace02
Audit this contract →
← previous block
·
next block →
recent activity