pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,287,493
← previous block
next block →
recent activity
Analyzing
Block #74,287,493
11 transactions · 11 stateful · 2026-05-13 08:50:03 UTC
Parallelism
64
/100
Blocked
27
%
Avg conflicts / tx
0.45
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,287,493
· 11 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
removeLiquidity
#2
0x1ffa3c9b
· blocks 3
#4
updateDataFeedsValuesPartial
#7
forward
#8
forward
#9
setData
#10
0x39435dac
#3
0x1094dc9f
· blocks 1
#5
0x0c7abd22
· blocks 1
#6
0xa09e9040
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w2
6
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf823e97f…2ee6
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xcf3283ba…c9fa
0x065c9d…c394
4 touches
1 conflict
0x2b523f4e…a062
0x065c9d…c394
3 touches
1 conflict
0x5d82c9b5…004c
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0004
0x5afd3e…7620
2 touches
0 conflicts
0x6f2599bd…646a
0x5afd3e…7620
2 touches
0 conflicts
0x9e45dad2…b2e8
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:
Kuru Exchange: Market-MON/USDC
3 conflicts on slot
0xf823e97fa0…262ee6
Audit this contract →
← previous block
·
next block →
recent activity