pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,623,609
← previous block
next block →
recent activity
Analyzing
Block #74,623,609
9 transactions · 7 stateful · 2026-05-14 22:14:40 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,623,609
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x84396f10
#3
0x98717539
· blocks 1
#5
0x0f6795d9
#6
0x0f6795d9
#7
updateDataFeedsValuesPartial
#8
setData
#4
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x06956408…967b
0x754704…b603
2 touches
0 conflicts
0x33f502ea…f39a
0x754704…b603
2 touches
0 conflicts
0x8f090681…a9cc
0x754704…b603
2 touches
0 conflicts
0xfd4bd0e6…5918
0x754704…b603
2 touches
0 conflicts
0x00000000…0002
0xab3526…fa38
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:
Perpl
1 conflict on slot
0x60f7fbaf90…97bd58
Audit this contract →
← previous block
·
next block →
recent activity