pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,306,733
← previous block
next block →
recent activity
Analyzing
Block #74,306,733
8 transactions · 7 stateful · 2026-05-13 10:58:10 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,306,733
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x719d975a
· blocks 1
#2
0x98717539
#3
updateDataFeedsValuesPartial
#4
setData
#5
0x62be7533
#6
0x6a0459b9
#7
swapExactIn
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4523ee0f…9634
0x699abc…6a3b
4 touches
1 conflict
0x928fafac…1c5a
0x699abc…6a3b
4 touches
1 conflict
0x928fafac…1c5b
0x699abc…6a3b
4 touches
1 conflict
0x00000000…003d
0x699abc…6a3b
4 touches
1 conflict
0xf56741e9…b391
0x699abc…6a3b
4 touches
1 conflict
0xf9cb2907…e7c8
0x699abc…6a3b
4 touches
1 conflict
0x335a161d…fe7f
0x000000…012a
4 touches
1 conflict
0x4523ee0f…9633
0x699abc…6a3b
4 touches
1 conflict
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
0x4523ee0f26…5f9634
Audit this contract →
← previous block
·
next block →
recent activity