pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,090,898
← previous block
next block →
recent activity
Analyzing
Block #75,090,898
11 transactions · 8 stateful · 2026-05-17 02:15:09 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,090,898
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
approve
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
claim
· blocks 1
#6
0x6a092525
#7
setData
#8
0x85a581…18db
#9
0x39435dac
#10
0x39435dac
#5
merklClaim
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x544ac270…ab6b
0x3bd359…433a
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0xdbadf6b0…43b2
0x33176b…e078
2 touches
0 conflicts
0x388f889f…a655
0x34b655…2a6f
2 touches
0 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
2 touches
0 conflicts
0x5e1ade3e…a22b
0x3ef3d8…d9ae
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:
Wrapped MON (WMON)
1 conflict on slot
0x544ac27000…59ab6b
Audit this contract →
← previous block
·
next block →
recent activity