pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#75,478,661
← previous block
next block →
recent activity
Analyzing
Block #75,478,661
10 transactions · 8 stateful · 2026-05-18 21:26:02 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,478,661
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
· blocks 2
#3
0x1a945f9c
#4
updatePriceFeedsIfNecessary
#5
0xed82b078
#6
0xed82b078
#7
updateDataFeedsValuesPartial
#8
setData
#2
0xed82b078
#9
0x044e7100
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0x094452…0a09
4 touches
1 conflict
0x846f2172…fd54
0x0555e3…2b9c
4 touches
1 conflict
0x00000000…0000
0x094452…0a09
4 touches
1 conflict
0x62e20208…be65
0x0555e3…2b9c
4 touches
1 conflict
0x00f7e3b7…e015
0x188d58…ea8e
4 touches
1 conflict
0x2f88a23f…9dc5
0x2a68ba…90c5
4 touches
1 conflict
0x9e223b01…38b2
0x3bd359…433a
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
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:
0x0944526d…170a09
1 conflict on slot
0x0000000000…000004
Audit this contract →
← previous block
·
next block →
recent activity