pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,238,770
← previous block
next block →
recent activity
Analyzing
Block #74,238,770
12 transactions · 5 stateful · 2026-05-13 03:26:11 UTC
Parallelism
83
/100
Blocked
20
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,238,770
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x4500f50f
#2
0x9609049f
#3
0xef555769
#4
0x0c7abd22
· blocks 1
#5
0x05ee6a22
#7
0x62be7533
#8
updateDataFeedsValuesPartial
#9
0x6a03efcb
#10
setData
#11
0x8b23406f
#6
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3f331a1…7b31
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xd46b4bd0…c2fd
0x065c9d…c394
2 touches
0 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x438cf5f6…f077
0x2a68ba…90c5
2 touches
0 conflicts
0x0d622e34…0000
0x681e90…ae09
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
0xe3f331a135…527b31
Audit this contract →
← previous block
·
next block →
recent activity