pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,318,291
← previous block
next block →
recent activity
Analyzing
Block #74,318,291
10 transactions · 10 stateful · 2026-05-13 12:15:03 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,318,291
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x98717539
· blocks 1
#3
0xd10227eb
#4
relay
#5
forward
#6
updateDataFeedsValuesPartial
#7
0xe9316489
#8
setData
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4db74a88…1c46
0x34b655…2a6f
4 touches
1 conflict
0xbad68552…e6bf
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x18b81ade…81be
0x34b655…2a6f
2 touches
0 conflicts
0x414e9446…4b59
0x34b655…2a6f
2 touches
0 conflicts
0x4e39aafd…796e
0x34b655…2a6f
2 touches
0 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
2 touches
0 conflicts
0x85a88798…f85e
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:
0x34b6552d…112a6f
1 conflict on slot
0x4db74a882c…c21c46
Audit this contract →
← previous block
·
next block →
recent activity