pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,284,000
← previous block
next block →
recent activity
Analyzing
Block #74,284,000
10 transactions · 9 stateful · 2026-05-13 08:26:51 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,284,000
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exactOutputSingle
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
forward
#5
0x6a043643
#6
setData
#7
swapExactIn
· blocks 1
#9
0x39435dac
#8
swapExactIn
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd967976…5491
0x699abc…6a3b
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x335a161d…fe7f
0x000000…012a
4 touches
1 conflict
0x6bfffdcd…7d7b
0x699abc…6a3b
3 touches
1 conflict
0x4245e4e8…096e
0x000000…012a
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
2 touches
0 conflicts
0x68faa0b9…14af
0x368ee5…7ca4
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:
0x699abc15…c86a3b
1 conflict on slot
0xdd96797657…005491
Audit this contract →
← previous block
·
next block →
recent activity