pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,239,306
← previous block
next block →
recent activity
Analyzing
Block #74,239,306
8 transactions · 7 stateful · 2026-05-13 03:29:46 UTC
Parallelism
63
/100
Blocked
29
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,239,306
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute
· blocks 2
#4
updateDataFeedsValuesPartial
#5
setData
#6
forward
#7
0x6a03f0a2
#2
execute
· blocks 1
#3
execute
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x83fef3…da03
6 touches
3 conflicts
0x00000000…0001
0x83fef3…da03
6 touches
3 conflicts
0x9015b6b2…142f
0x3bd359…433a
6 touches
3 conflicts
0xaa460b01…853c
0x754704…b603
6 touches
3 conflicts
0xdbadf6b0…43b2
0x33176b…e078
2 touches
0 conflicts
0x0d622e34…0000
0x681e90…ae09
2 touches
0 conflicts
0x16953d29…2b24
0x754704…b603
2 touches
0 conflicts
0x47c84536…ce50
0x754704…b603
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:
0x83fef384…6fda03
3 conflicts on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity