pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,091,001
← previous block
next block →
recent activity
Analyzing
Block #76,091,001
12 transactions · 6 stateful · 2026-05-21 17:36:25 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,091,001
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x000000b2
#4
updateDataFeedsValuesPartial
#5
forward
#6
setData
#7
0x1e5c4a…b251
#8
0x365398…9413
#9
0xb1d1dc…cdc6
#10
0xee4210…411a
#11
0x39435dac
#2
0x0c7abd22
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
0x0d8a5740…a77b
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x3610ec01…67b9
0x065c9d…c394
2 touches
0 conflicts
0x41755291…977f
0x065c9d…c394
2 touches
0 conflicts
0x44c29306…91f8
0x065c9d…c394
2 touches
0 conflicts
0xead4c397…838a
0x065c9d…c394
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:
FastLane: FastLaneAuctionHandler
1 conflict on slot
0x0d8a574018…8ea77b
Audit this contract →
← previous block
·
next block →
recent activity