pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,383,188
← previous block
next block →
recent activity
Analyzing
Block #74,383,188
10 transactions · 7 stateful · 2026-05-13 19:26:46 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,383,188
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updatePosition
#3
setData
#4
0x39435dac
#5
0x39435dac
#6
0x39435dac
#7
0x39435dac
· blocks 1
#9
0x39435dac
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef17b8cd…9511
0x34b655…2a6f
4 touches
1 conflict
0x9b36f19f…fa5a
0x34b655…2a6f
4 touches
1 conflict
0xa3ff1ab2…8ae3
0x34b655…2a6f
4 touches
1 conflict
0xa27fa22d…7dca
0x54cd53…9e7d
2 touches
0 conflicts
0xd1a0adf6…6e55
0x54cd53…9e7d
2 touches
0 conflicts
0x08abfabe…4041
0x6657d1…8ccc
2 touches
0 conflicts
0x1fe06971…bfb8
0x6657d1…8ccc
2 touches
0 conflicts
0x3e0aef53…ccff
0x6657d1…8ccc
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:
0x34b6552d…112a6f
1 conflict on slot
0xef17b8cd5c…709511
Audit this contract →
← previous block
·
next block →
recent activity