pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,257,037
← previous block
next block →
recent activity
Analyzing
Block #74,257,037
8 transactions · 7 stateful · 2026-05-13 05:27:35 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,257,037
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
swapExactIn
· blocks 1
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x6a040c3e
#7
setData
#3
swapExactIn
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x335a161d…fe7f
0x000000…012a
4 touches
1 conflict
0x358f0211…f2b9
0x699abc…6a3b
4 touches
1 conflict
0x6fe7bf93…0d0c
0x699abc…6a3b
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x33346fc8…fc57
0x065c9d…c394
2 touches
0 conflicts
0x7b405c92…7d77
0x065c9d…c394
2 touches
0 conflicts
0xb3f05567…30b0
0x065c9d…c394
2 touches
0 conflicts
0xc2c6fb3d…a866
0x065c9d…c394
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:
AUSD (AUSD)
1 conflict on slot
0x335a161d76…bdfe7f
Audit this contract →
← previous block
·
next block →
recent activity