pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,288,413
← previous block
next block →
recent activity
Analyzing
Block #74,288,413
9 transactions · 5 stateful · 2026-05-13 08:56:10 UTC
Parallelism
78
/100
Blocked
20
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,288,413
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x0c7abd22
· blocks 1
#4
0xed82b078
#5
0x6a043d22
#6
setData
#7
0x695ed0…4243
#8
0xb8462e…c198
#3
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xcf3283ba…c9fa
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x33b849aa…8100
0x065c9d…c394
2 touches
0 conflicts
0x3ac58178…c1bf
0x065c9d…c394
2 touches
0 conflicts
0x6546b442…16a8
0x065c9d…c394
2 touches
0 conflicts
0x83f254ff…6d61
0x065c9d…c394
2 touches
0 conflicts
0x84549c35…e36d
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity