pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,705,987
← previous block
next block →
recent activity
Analyzing
Block #73,705,987
8 transactions · 7 stateful · 2026-05-10 16:08:52 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,705,987
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
· blocks 1
#2
updateDataFeedsValuesPartial
#3
setData
#4
0x0c7abd22
#6
0x6a00ae0c
#7
0x39435dac
#5
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb245fe36…d765
0x34b655…2a6f
4 touches
1 conflict
0x40b3d30e…7b92
0x34b655…2a6f
4 touches
1 conflict
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0x408e66bb…3d6b
0x34b655…2a6f
2 touches
0 conflicts
0x44039c64…0de6
0x34b655…2a6f
2 touches
0 conflicts
0x462d8e25…1e49
0x34b655…2a6f
2 touches
0 conflicts
0x56f8b3c0…8a5e
0x34b655…2a6f
2 touches
0 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0xb245fe3647…73d765
Audit this contract →
← previous block
·
next block →
recent activity