pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,356,754
← previous block
next block →
recent activity
Analyzing
Block #74,356,754
10 transactions · 10 stateful · 2026-05-13 16:30:49 UTC
Parallelism
70
/100
Blocked
30
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,356,754
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 3
#3
updatePrices
#4
0x98717539
#5
updateDataFeedsValuesPartial
#6
setData
#9
0x39435dac
#2
0xed82b078
· blocks 1
#8
0x5339c59f
#7
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
7
w2
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41755291…977f
0x065c9d…c394
6 touches
3 conflicts
0x269e04b4…8870
0x065c9d…c394
3 touches
1 conflict
0xa856bed4…4639
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x40ecd90c…10ed
0x065c9d…c394
2 touches
0 conflicts
0x54b111f9…3295
0x065c9d…c394
2 touches
0 conflicts
0x7151743b…4101
0x065c9d…c394
2 touches
0 conflicts
0x952e5c70…8637
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
3 conflicts on slot
0x4175529119…79977f
Audit this contract →
← previous block
·
next block →
recent activity