pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,478,582
← previous block
next block →
recent activity
Analyzing
Block #76,478,582
12 transactions · 10 stateful · 2026-05-23 12:37:18 UTC
Parallelism
67
/100
Blocked
40
%
Avg conflicts / tx
0.42
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,478,582
· 12 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x39ecce49
#7
updateDataFeedsValuesPartial
#8
setData
#9
forward
#10
execFwdPositionOps
#11
execFwdPositionOps
#2
0x0c7abd22
· blocks 2
#4
0xed82b078
· blocks 2
#5
batchUpdate
#6
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
5
w3
6
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8bc3e255…0a0b
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x3bd55803…5d4c
0x1b6862…e19c
4 touches
1 conflict
0x0bd261be…21c6
0xa6afd3…d132
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
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:
Kuru Exchange: Market-WETH/USDC
3 conflicts on slot
0x8bc3e2552c…6c0a0b
Audit this contract →
← previous block
·
next block →
recent activity