pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#75,098,242
← previous block
next block →
recent activity
Analyzing
Block #75,098,242
11 transactions · 9 stateful · 2026-05-17 03:04:02 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,098,242
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x98717539
#2
0x1ffa3c9b
· blocks 2
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0x19c543…8ff3
#8
0xda2e17…f719
#9
setData
#10
0x39435dac
#3
0xed82b078
· blocks 1
#4
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x064c332a…9152
0x065c9d…c394
2 touches
0 conflicts
0x2cb71ff5…4e6a
0x065c9d…c394
2 touches
0 conflicts
0x3b98836c…9952
0x065c9d…c394
2 touches
0 conflicts
0xcc072c14…bb0a
0x065c9d…c394
2 touches
0 conflicts
0xfa0b7a20…2982
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:
0x065c9d28…a9c394
3 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity