pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,310,040
← previous block
next block →
recent activity
Analyzing
Block #75,310,040
12 transactions · 10 stateful · 2026-05-18 02:39:21 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,310,040
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
removeLiquidity
#2
0xab083028
#3
0x98717539
· blocks 1
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
setData
#7
forward
#8
forward
#9
0x6a0a7c50
#11
0x39435dac
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x544745e8…d72e
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0xb69d0f88…b40d
0x065c9d…c394
2 touches
0 conflicts
0xbc05ab44…eb5b
0x065c9d…c394
2 touches
0 conflicts
0xe3bc2de9…ce74
0x065c9d…c394
2 touches
0 conflicts
0xe8583ba8…f63b
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:
Perpl
1 conflict on slot
0x544745e82f…47d72e
Audit this contract →
← previous block
·
next block →
recent activity