pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,306,908
← previous block
next block →
recent activity
Analyzing
Block #75,306,908
11 transactions · 11 stateful · 2026-05-18 02:18:20 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,306,908
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
withdraw
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x5339c59f
#5
0x5339c59f
#6
0x6a0a7764
#7
closeBetting
#8
setData
#10
0x39435dac
#9
swapExactIn
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf831072…51d5
0x80f006…d585
4 touches
1 conflict
0xaf831072…51d6
0x80f006…d585
4 touches
1 conflict
0x00000000…0036
0x386489…7508
4 touches
1 conflict
0xa8669ab5…6af7
0x754704…b603
4 touches
1 conflict
0x10d80fee…dbda
0x1d1325…2305
2 touches
0 conflicts
0x8cf3d245…1d0d
0x1d1325…2305
2 touches
0 conflicts
0xdb067026…9eb8
0x1d1325…2305
2 touches
0 conflicts
0x99a21305…dffc
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:
0x80f00661…45d585
1 conflict on slot
0xaf831072f6…c551d5
Audit this contract →
← previous block
·
next block →
recent activity