pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,254,780
← previous block
next block →
recent activity
Analyzing
Block #74,254,780
10 transactions · 6 stateful · 2026-05-13 05:12:35 UTC
Parallelism
80
/100
Blocked
17
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,254,780
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
#2
airdropToken
#3
updateDataFeedsValuesPartial
#4
0x5339c59f
· blocks 1
#6
0x6a0408ba
#7
0xe4413c…7842
#8
0x194fba…d5e3
#9
setData
#5
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf3283ba…c9fa
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1e664962…0631
0x23c26b…7777
2 touches
0 conflicts
0x2cc9a469…d64c
0x23c26b…7777
2 touches
0 conflicts
0x649b898a…82be
0x23c26b…7777
2 touches
0 conflicts
0x6805730d…42bd
0x23c26b…7777
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
1 conflict on slot
0xcf3283bab2…c3c9fa
Audit this contract →
← previous block
·
next block →
recent activity