pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,681,385
← previous block
next block →
recent activity
Analyzing
Block #75,681,385
10 transactions · 8 stateful · 2026-05-19 20:07:12 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,681,385
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
· blocks 1
#1
0x7864c218
#2
0xab083028
#3
0x0f6795d9
#4
0x0f6795d9
#5
updateDataFeedsValuesPartial
#7
0x6a0cc368
#8
setData
#9
setApprovalForAll
#6
claimRewards
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
0
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09000000…0007
0x000000…1000
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x460f40ad…b1dc
0x065c9d…c394
2 touches
0 conflicts
0x86c8edc0…f40f
0x065c9d…c394
2 touches
0 conflicts
0xb2513d25…7517
0x065c9d…c394
2 touches
0 conflicts
0xb59f2783…d9f1
0x065c9d…c394
2 touches
0 conflicts
0xc6d4aba5…aac2
0x065c9d…c394
2 touches
0 conflicts
0xcc4f1f14…aa5f
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:
Monad: Staking
1 conflict on slot
0x0900000000…000007
Audit this contract →
← previous block
·
next block →
recent activity