pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,306,955
← previous block
next block →
recent activity
Analyzing
Block #74,306,955
11 transactions · 9 stateful · 2026-05-13 10:59:39 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,306,955
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
execute
#3
updateDataFeedsValuesPartial
#4
0x5bf9264c
#5
0x5bf9264c
#6
swapExactIn
· blocks 1
#7
0xc5a04723
#8
setData
#10
0x39435dac
#9
swapExactIn
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x335a161d…fe7f
0x000000…012a
4 touches
1 conflict
0x001d0b35…a0bc
0x699abc…6a3b
4 touches
1 conflict
0x928fafac…1c5a
0x699abc…6a3b
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xc6f1b3af…c97c
0x1001ff…1001
2 touches
0 conflicts
0x00000000…0000
0x276664…5732
2 touches
0 conflicts
0x00000000…0002
0x276664…5732
2 touches
0 conflicts
0x00000000…0004
0x276664…5732
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:
0x00000000…a9012a
1 conflict on slot
0x335a161d76…bdfe7f
Audit this contract →
← previous block
·
next block →
recent activity