pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,624,188
← previous block
next block →
recent activity
Analyzing
Block #74,624,188
10 transactions · 8 stateful · 2026-05-14 22:18:34 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,624,188
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
flash
#2
removeLiquidity
#3
0xed82b078
· blocks 2
#4
updateDataFeedsValuesPartial
#7
forward
#8
0x6a064ab2
#9
setData
#5
0xccf50a51
· blocks 1
#6
0xccf50a51
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x968bdacb…f461
0x2a68ba…90c5
6 touches
3 conflicts
0x1d2cb982…2172
0x065c9d…c394
5 touches
3 conflicts
0x6677f92f…b7cd
0x0555e3…2b9c
4 touches
1 conflict
0x9e223b01…38b2
0x3bd359…433a
4 touches
1 conflict
0x846f2172…fd54
0x0555e3…2b9c
4 touches
1 conflict
0x00000000…0000
0x094452…0a09
4 touches
1 conflict
0x00000000…0003
0x094452…0a09
4 touches
1 conflict
0x00000000…0004
0x094452…0a09
4 touches
1 conflict
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:
0x2a68ba18…8e90c5
3 conflicts on slot
0x968bdacb8d…ddf461
Audit this contract →
← previous block
·
next block →
recent activity