pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,921,065
← previous block
next block →
recent activity
Analyzing
Block #74,921,065
11 transactions · 10 stateful · 2026-05-16 07:19:55 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,921,065
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
removeLiquidity
#2
0x98717539
· blocks 1
#3
0xd10227eb
#4
0x0c7abd22
#5
forward
#6
updateDataFeedsValuesPartial
#7
0x64480813
#8
setData
#9
0x6a081b13
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x6ee86c0c…50c6
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x10f5f4d8…572e
0x34b655…2a6f
2 touches
0 conflicts
0x32589dde…a20c
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…0004
0x5afd3e…7620
2 touches
0 conflicts
0x1c692b9f…10d0
0x5afd3e…7620
2 touches
0 conflicts
0xc36654ed…58d6
0x5afd3e…7620
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
0xac2a02739b…81721b
Audit this contract →
← previous block
·
next block →
recent activity