pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#75,103,840
← previous block
next block →
recent activity
Analyzing
Block #75,103,840
10 transactions · 5 stateful · 2026-05-17 03:41:20 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,103,840
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x1094dc9f
#4
0xe3a3c9cc
#5
createModule
#6
updateDataFeedsValuesPartial
#7
0x6a093958
#8
setData
#9
exactInputSingle
#2
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0xb6d6d740…e91a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x0f72b83f…a923
0xd32edf…ff58
3 touches
1 conflict
0x47b110be…9876
0x065c9d…c394
2 touches
0 conflicts
0xb49739f5…c4ba
0x065c9d…c394
2 touches
0 conflicts
0xc2ef7224…f3fa
0x065c9d…c394
2 touches
0 conflicts
0xe673c2d9…82aa
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:
0x1b68626d…2de19c
1 conflict on slot
0x0000000000…000013
Audit this contract →
← previous block
·
next block →
recent activity