pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,664,141
← previous block
next block →
recent activity
Analyzing
Block #73,664,141
11 transactions · 9 stateful · 2026-05-10 11:26:26 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,664,141
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xe0de3ed7
#2
0x121eab2f
#3
updateDataFeedsValuesPartial
#4
0x62be7533
· blocks 1
#6
commit
#7
0x6a006bda
#8
setData
#9
0x0c7abd22
#10
modifyLiquidities
#5
createModule
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4aa4f53b…899f
0x188d58…ea8e
4 touches
1 conflict
0x4aa4f53b…89a1
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0000
0x249978…5353
4 touches
1 conflict
0x00000000…0001
0x249978…5353
4 touches
1 conflict
0x00000000…0003
0x249978…5353
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
4 touches
1 conflict
0xd56db188…ecd0
0x000000…012a
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
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:
0x188d586d…f9ea8e
1 conflict on slot
0x4aa4f53bc4…b2899f
Audit this contract →
← previous block
·
next block →
recent activity