pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,477,202
← previous block
next block →
recent activity
Analyzing
Block #76,477,202
13 transactions · 9 stateful · 2026-05-23 12:28:07 UTC
Parallelism
85
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,477,202
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
exactOutputSingle
· blocks 1
#3
exactOutputSingle
#4
execute
#5
commitVerification
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0xed82b078
#9
redeemDelegations
#11
setData
#12
exactInputSingle
#10
0x45761772
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0003
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0004
0x63e48b…53f2
4 touches
1 conflict
0x9a555477…19a8
0x754704…b603
4 touches
1 conflict
0x00000000…0004
0x0594c7…a3be
2 touches
0 conflicts
0x00000000…0005
0x0594c7…a3be
2 touches
0 conflicts
0x3c754b0f…e8a5
0x0594c7…a3be
2 touches
0 conflicts
0x683afda8…faaf
0x0594c7…a3be
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:
0x63e48b72…8c53f2
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity