pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#81,008,618
← previous block
next block →
recent activity
Analyzing
Block #81,008,618
9 transactions · 8 stateful · 2026-06-13 12:13:36 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#81,008,618
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
approve
· blocks 1
#3
0xab083028
#4
0x39435dac
#5
updateDataFeedsValuesPartial
#6
0x6a2d49e7
#7
setData
#8
0xc7e3ec2c
#2
deposit
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
0x487d2922…28b6
0x754704…b603
2 touches
1 conflict
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
2 touches
0 conflicts
0x0f758260…e245
0x34b655…2a6f
2 touches
0 conflicts
0xbb9fbe04…cd71
0x34b655…2a6f
2 touches
0 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
2 touches
0 conflicts
0xed324c8e…b866
0x34b655…2a6f
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
0x487d2922ff…7828b6
Audit this contract →
← previous block
·
next block →
recent activity