pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,781,303
← previous block
next block →
recent activity
Analyzing
Block #75,781,303
13 transactions · 7 stateful · 2026-05-20 07:11:55 UTC
Parallelism
85
/100
Blocked
14
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,781,303
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a0d5f33
#2
0x6a0d5f33
#3
updatePosition
#4
collect
#5
0xed82b078
· blocks 1
#7
updateDataFeedsValuesPartial
#8
0x6a0d5f33
#9
0xb5b668…f0c2
#10
0x71fa52…4240
#11
setData
#12
0x6a0d5f33
#6
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2f1c865b…052a
0x3bd359…433a
2 touches
0 conflicts
0xa27fa22d…7dca
0x54cd53…9e7d
2 touches
0 conflicts
0x0242c806…52b1
0x6657d1…8ccc
2 touches
0 conflicts
0x335ed210…e60c
0x6657d1…8ccc
2 touches
0 conflicts
0x3ab3d5c7…2de5
0x6657d1…8ccc
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity