pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,949,382
← previous block
next block →
recent activity
Analyzing
Block #75,949,382
13 transactions · 11 stateful · 2026-05-21 01:52:46 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,949,382
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exactOutputSingle
#2
0xed82b078
#3
updateDataFeedsValuesPartial
#4
updatePrices
#5
updatePrices
#6
0x5bf9264c
· blocks 1
#8
forward
#9
0xed82b078
#10
0xed82b078
#11
receiveMessage
#12
setData
#7
0x5bf9264c
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x18aed20c…48f3
0x000000…012a
2 touches
0 conflicts
0x4245e4e8…096e
0x000000…012a
2 touches
0 conflicts
0x00000000…000b
0x097d40…9920
2 touches
0 conflicts
0x76e96198…eec4
0x2a68ba…90c5
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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
0x22e0cc1d4a…90ad04
Audit this contract →
← previous block
·
next block →
recent activity