pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,591,537
← previous block
next block →
recent activity
Analyzing
Block #75,591,537
10 transactions · 8 stateful · 2026-05-19 10:06:33 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,591,537
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
· blocks 1
#2
0xab083028
· blocks 1
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
withdraw
#7
0x6a0c36a1
#8
setData
#9
0x39435dac
#3
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x443a3e47…f4a4
0x065c9d…c394
4 touches
1 conflict
0xd1644788…68bd
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0x25a8f509…ace7
0x065c9d…c394
3 touches
1 conflict
0xbfff5ce9…80e0
0x065c9d…c394
3 touches
1 conflict
0xdb067026…9eb8
0x1d1325…2305
2 touches
0 conflicts
0x2f88a23f…9dc5
0x2a68ba…90c5
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
0x443a3e479f…3af4a4
Audit this contract →
← previous block
·
next block →
recent activity