pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,351,849
← previous block
next block →
recent activity
Analyzing
Block #74,351,849
13 transactions · 12 stateful · 2026-05-13 15:58:07 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,351,849
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xe9cef6…fcb3
#2
0x1ffa3c9b
#3
exactOutputSingle
#4
updatePrices
#5
0x98717539
#6
forward
#7
exactInputSingle
· blocks 1
#9
updateDataFeedsValuesPartial
#10
0x6a04a006
#11
approve
#12
setData
#8
exactInputSingle
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
0x3f1434d4…1ce1
0x3bd359…433a
4 touches
1 conflict
0x3f1434d4…1ce1
0x11ed3b…2c96
4 touches
1 conflict
0x00000000…0000
0x2d59fc…cd50
4 touches
1 conflict
0x00000000…0003
0x2d59fc…cd50
4 touches
1 conflict
0x4245e4e8…096e
0x000000…012a
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x47b807a2…3307
0x065c9d…c394
2 touches
0 conflicts
0x96db9c58…9494
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:
0x3bd359c1…15433a
1 conflict on slot
0x3f1434d4b2…9e1ce1
Audit this contract →
← previous block
·
next block →
recent activity