pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,230,437
← previous block
next block →
recent activity
Analyzing
Block #76,230,437
10 transactions · 9 stateful · 2026-05-22 09:05:13 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,230,437
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x98717539
#2
redeemDelegations
#3
0x0c7abd22
#4
executeBatch
· blocks 1
#6
0x6df9e92b
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
setData
#5
executeBatch
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd58b5c38…3b7c
0x754704…b603
4 touches
1 conflict
0x5149ba0e…d954
0x754704…b603
4 touches
1 conflict
0x0b0c2e8d…c1b8
0xe52b14…7230
4 touches
1 conflict
0x532023a5…d800
0xe52b14…7230
4 touches
1 conflict
0x8ffa3328…ce11
0xe52b14…7230
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0xcb45d9d6…cb87
0x1b6862…e19c
2 touches
0 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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:
USDC (USDC)
1 conflict on slot
0xd58b5c380d…8f3b7c
Audit this contract →
← previous block
·
next block →
recent activity