pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#75,196,407
← previous block
next block →
recent activity
Analyzing
Block #75,196,407
8 transactions · 7 stateful · 2026-05-17 13:59:21 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
#75,196,407
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
swap
#2
0x1ffa3c9b
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0xd53e7c84
#6
0x6a09ca31
#7
setData
#5
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x577f1df9…0947
0x065c9d…c394
4 touches
1 conflict
0x8167bdd1…31ed
0x065c9d…c394
3 touches
1 conflict
0x094f75c8…15d2
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x231b27ec…9d8f
0x065c9d…c394
2 touches
0 conflicts
0x7ea17875…b3a7
0x065c9d…c394
2 touches
0 conflicts
0x890a7265…5428
0x065c9d…c394
2 touches
0 conflicts
0xba38536d…2b7d
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
1 conflict on slot
0x577f1df90a…e20947
Audit this contract →
← previous block
·
next block →
recent activity