pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,359,315
← previous block
next block →
recent activity
Analyzing
Block #74,359,315
9 transactions · 8 stateful · 2026-05-13 16:47:48 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,359,315
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
updatePrices
#4
updateDataFeedsValuesPartial
#5
setData
#7
0x5339c59f
#8
0x39435dac
#2
0xed82b078
· blocks 1
#6
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x045a927d…5a1e
0x065c9d…c394
2 touches
0 conflicts
0x0cec9298…f69e
0x065c9d…c394
2 touches
0 conflicts
0x6a1938e1…d49f
0x065c9d…c394
2 touches
0 conflicts
0xba809423…9b52
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:
0x065c9d28…a9c394
1 conflict on slot
0x4175529119…79977f
Audit this contract →
← previous block
·
next block →
recent activity